Reduced-size notification interface

ABSTRACT

An electronic device with a touch-sensitive display can obtain a plurality of alerts associated with dates and times. The device can detect a user input, and in response to the input display a notification interface. The notification interface can include a future notification representing a future alert with a date and time after the current date and time, and a past notification representing a past alert with a date and time before the current date and time. The future and past notifications can be separated by a graphical separator that has an indication of the current time. The future and past alerts correspond to different installed applications.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationSer. No. 62/044,953, “Reduced-Size Notification Interface,” filed onSep. 2, 2014, and to U.S. Provisional Application Ser. No. 62/129,924,“Reduced-Size Notification Interface,” filed on Mar. 8, 2015. Thecontent of these applications is hereby incorporated by reference forall purposes.

This application relates to U.S. Provisional Patent Application Ser. No.62/044,894 entitled “Reduced-Size Interfaces for Managing Alerts,” filedSep. 2, 2014; U.S. Provisional Patent Application Ser. No. 62/129,818entitled “Reduced-Size Interfaces for Managing Alerts,” filed Mar. 7,2015; U.S. Provisional Patent Application Ser. No. 62/044,990 entitled“Physical Activity and Workout Monitor,” filed Sep. 2, 2014; co-pendingU.S. Provisional Patent Application Ser. No. 62/129,828 entitled“Physical Activity and Workout Monitor,” filed Mar. 7, 2015; co-pendingU.S. patent application Ser. No. 14/475,446 entitled “Coordination ofMessage Alert Presentations Across Devices Based on Device Modes,” filedSep. 2, 2014; co-pending U.S. patent application Ser. No. 14/475,471entitled “Message Processing By Subscriber App Prior To MessageForwarding,” filed Sep. 2, 2014; International Patent Application SerialNo. PCT/US2013/040061, entitled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013 and International Patent ApplicationSerial No. PCT/US2013/069483, entitled “Device, Method, and GraphicalUser Interface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013. The contents of these applicationsare hereby incorporated by reference in their entirety.

FIELD

The disclosed examples relate generally to user interfaces of electronicdevices, and more specifically to techniques for displaying and managingalert notifications.

BACKGROUND

Reduced-size electronic devices (e.g., devices that are smaller thantypical cellular phones) that are designed to be worn by a user canconveniently display notifications for a wide variety of alerts, such ascalendar alerts, emails, clock alarms, stock market alerts, and textmessages. The relatively small screen size of a reduced-size electronicdevice may limit the amount of information that can be comfortablyviewed, however, thus limiting the number of notifications that can bedisplayed on a single screen and increasing the importance ofprioritizing display of relevant information.

SUMMARY

In accordance with some embodiments, a method is performed at anelectronic device with a touch-sensitive display. The method includes:obtaining a plurality of alerts associated with date-times; detecting auser input; in response to detecting the user input: obtaining a currentdate-time, and displaying a notification interface on the display, thenotification interface comprising: a first notification representing afirst alert of the plurality of alerts associated with a date-time afterthe current date-time, a second notification representing a second alertof the plurality of alerts associated with a date-time before thecurrent date-time, and a graphical separator between the firstnotification and the second notification, wherein the graphicalseparator comprises an indication of the current date-time, wherein thefirst alert and the second alert correspond to different installedapplications.

In accordance with some embodiments, a method is performed at anelectronic device with a touch-sensitive display. The method includes:obtaining a plurality of alerts associated with date-times; detecting afirst user input; in response to detecting the first user input:obtaining a first current date-time, and displaying a plurality of pastnotifications representing a plurality of past alerts from the pluralityof alerts, wherein the plurality of past alerts are associated withdate-times before the current date-time, and wherein the plurality ofpast alerts correspond to a first plurality of installed applications;detecting a contact on the touch-sensitive display; determining whetherthe contact is a tap or a substantially horizontal swipe; in response toa determination that the contact is a substantially horizontal swipe:obtaining a second current date-time, and displaying a plurality offuture notifications representing a plurality of future alerts from theplurality of alerts, wherein the plurality of future alerts areassociated with date-times after the second current date-time, andwherein the plurality of future alerts correspond to a second pluralityof installed applications.

In accordance with some embodiments, a method is performed at anelectronic device with a touch-sensitive display. The method includes:obtaining a plurality of alerts associated with date-times; detecting afirst user input; in response to detecting the first user input:obtaining a first current date-time; displaying a plurality of futurenotifications representing a plurality of future alerts from theplurality of alerts, wherein the plurality of future alerts areassociated with date-times after the first current date-time, andwherein the plurality of future alerts correspond to a first pluralityof installed applications; detecting a contact on the display;determining whether the contact is a tap or a substantially horizontalswipe; in accordance with a determination that the contact is asubstantially horizontal swipe: obtaining a second current date-time;and displaying a plurality of past notifications representing aplurality of past alerts from the plurality of alerts, wherein theplurality of past alerts are associated with date-times before thesecond current date-time, and wherein the plurality of past alertscorrespond to a second plurality of installed applications.

In accordance with some embodiments, a method is performed at anelectronic device with a touch-sensitive display. The method includes:obtaining a plurality of alerts associated with date-times; detecting afirst user input; in response to detecting the first user input:obtaining a first current date-time; displaying a plurality of futurenotifications representing a plurality of future alerts from theplurality of alerts, wherein the plurality of future alerts areassociated with date-times after the first current date-time, andwherein the plurality of future alerts correspond to a first pluralityof installed applications; detecting a contact on the display;determining whether the contact is a tap or a substantially horizontalswipe; in accordance with a determination that the contact is asubstantially horizontal swipe: obtaining a second current date-time;and displaying a plurality of past notifications representing aplurality of past alerts from the plurality of alerts, wherein theplurality of past alerts are associated with date-times before thesecond current date-time, and wherein the plurality of past alertscorrespond to a second plurality of installed applications.

In accordance with some embodiments, a method is performed at anelectronic device with a touch-sensitive display and a rotatable inputmechanism. The method includes: obtaining a plurality of alerts;displaying a first set of user interface objects; detecting a rotationof the rotatable input mechanism; in response to detecting the rotation:determining whether the first set of user interface objects meets athreshold criteria; in accordance with a determination that the firstset of user interface objects meets the threshold criteria, replacingdisplay of the first set of user interface objects with display of aplurality of notifications representing at least a subset of theplurality of alerts; and in accordance with a determination that thefirst set of user interface objects does not meet the thresholdcriteria, displaying a second set of user interface objects, wherein thesecond set is larger than the first set and comprises the first set.

In accordance with some embodiments, a method is performed at anelectronic device with a touch-sensitive display, the electronic devicehaving an installed application, the electronic device configured tocommunicate wirelessly with an external device. The method includes:receiving application data associated with the installed application;displaying, on the touch-sensitive display of the electronic device, afirst indication indicating receipt of the application data; receiving auser's indication indicating whether the electronic device is toinstruct the external device to display an indication indicatingreceipt, by the electronic device, of application data associated withthe installed application; and in response to the user's indication toinstruct the external device: sending data to the external device,wherein the data causes the external device to display a secondindication indicating receipt of the application data.

In accordance with some embodiments, a method is performed at anelectronic device with a touch-sensitive display. The method includes:receiving a plurality of alerts, wherein the alerts are associated withdate-times, wherein the alerts include content, and wherein the alertscorrespond to a plurality of installed applications; detecting a userinput; and in response to detecting the user input, displaying anotification interface on the display, the notification interfacecomprising a plurality of notifications representing at least a subsetof the plurality of alerts, wherein the notifications are displayed in achronological order based on the date-times associated with the alerts,and wherein the notifications include user interface objectsrepresentative of the corresponding installed applications of thealerts, and wherein the notifications include at least a portion of thecontent of the plurality of alerts.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display cause the electronicdevice to: obtain a plurality of alerts associated with date-times;detect a user input; in response to detecting the user input: obtain acurrent date-time, and display a notification interface on the display,the notification interface comprising: a first notification representinga first alert of the plurality of alerts associated with a date-timeafter the current date-time, a second notification representing a secondalert of the plurality of alerts associated with a date-time before thecurrent date-time, and a graphical separator between the firstnotification and the second notification, wherein the graphicalseparator comprises an indication of the current date-time, wherein thefirst alert and the second alert correspond to different installedapplications.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display cause the electronicdevice to: obtain a plurality of alerts associated with date-times;detect a first user input; in response to detecting the first userinput: obtain a first current date-time, and display a plurality of pastnotifications representing a plurality of past alerts from the pluralityof alerts, wherein the plurality of past alerts are associated withdate-times before the current date-time, and wherein the plurality ofpast alerts correspond to a first plurality of installed applications;detect a contact on the touch-sensitive display; determine whether thecontact is a tap or a substantially horizontal swipe; in response to adetermination that the contact is a substantially horizontal swipe:obtain a second current date-time, and display a plurality of futurenotifications representing a plurality of future alerts from theplurality of alerts, wherein the plurality of future alerts areassociated with date-times after the second current date-time, andwherein the plurality of future alerts correspond to a second pluralityof installed applications.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display cause the electronicdevice to: obtain a plurality of alerts associated with date-times;detect a first user input; in response to detecting the first userinput: obtain a first current date-time; display a plurality of futurenotifications representing a plurality of future alerts from theplurality of alerts, wherein the plurality of future alerts areassociated with date-times after the first current date-time, andwherein the plurality of future alerts correspond to a first pluralityof installed applications; detect a contact on the display; determinewhether the contact is a tap or a substantially horizontal swipe; inaccordance with a determination that the contact is a substantiallyhorizontal swipe: obtain a second current date-time; and display aplurality of past notifications representing a plurality of past alertsfrom the plurality of alerts, wherein the plurality of past alerts areassociated with date-times before the second current date-time, andwherein the plurality of past alerts correspond to a second plurality ofinstalled applications.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display cause the electronicdevice to: obtain a plurality of alerts associated with date-times;detect a first user input; in response to detecting the first userinput: obtain a first current date-time; display a plurality of futurenotifications representing a plurality of future alerts from theplurality of alerts, wherein the plurality of future alerts areassociated with date-times after the first current date-time, andwherein the plurality of future alerts correspond to a first pluralityof installed applications; detect a contact on the display; determinewhether the contact is a tap or a substantially horizontal swipe; inaccordance with a determination that the contact is a substantiallyhorizontal swipe: obtain a second current date-time; and display aplurality of past notifications representing a plurality of past alertsfrom the plurality of alerts, wherein the plurality of past alerts areassociated with date-times before the second current date-time, andwherein the plurality of past alerts correspond to a second plurality ofinstalled applications.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display and a rotatableinput mechanism cause the electronic device to: obtain a plurality ofalerts; display a first set of user interface objects; detect a rotationof the rotatable input mechanism; in response to detecting the rotation:determine whether the first set of user interface objects meets athreshold criteria; in accordance with a determination that the firstset of user interface objects meets the threshold criteria, replacedisplay of the first set of user interface objects with display of aplurality of notifications representing at least a subset of theplurality of alerts; and in accordance with a determination that thefirst set of user interface objects does not meet the thresholdcriteria, display a second set of user interface objects, wherein thesecond set is larger than the first set and comprises the first set.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display, the electronicdevice having an installed application, the electronic device configuredto communicate wirelessly with an external device, cause the electronicdevice to: receive application data associated with the installedapplication; display, on the touch-sensitive display of the electronicdevice, a first indication indicating receipt of the application data;receive a user's indication indicating whether the electronic device isto instruct the external device to display an indication indicatingreceipt, by the electronic device, of application data associated withthe installed application; and in response to the user's indication toinstruct the external device: send data to the external device, whereinthe data causes the external device to display a second indicationindicating receipt of the application data.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display cause the electronicdevice to: receive a plurality of alerts, wherein the alerts areassociated with date-times, wherein the alerts include content, andwherein the alerts correspond to a plurality of installed applications;detect a user input; and in response to detecting the user input,display a notification interface on the display, the notificationinterface comprising a plurality of notifications representing at leasta subset of the plurality of alerts, wherein the notifications aredisplayed in a chronological order based on the date-times associatedwith the alerts, and wherein the notifications include user interfaceobjects representative of the corresponding installed applications ofthe alerts, and wherein the notifications include at least a portion ofthe content of the plurality of alerts.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display cause the electronicdevice to: obtain a plurality of alerts associated with date-times;detect a user input; in response to detecting the user input: obtain acurrent date-time, and display a notification interface on the display,the notification interface comprising: a first notification representinga first alert of the plurality of alerts associated with a date-timeafter the current date-time, a second notification representing a secondalert of the plurality of alerts associated with a date-time before thecurrent date-time, and a graphical separator between the firstnotification and the second notification, wherein the graphicalseparator comprises an indication of the current date-time, wherein thefirst alert and the second alert correspond to different installedapplications.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display cause the electronicdevice to: obtain a plurality of alerts associated with date-times;detect a first user input; in response to detecting the first userinput: obtain a first current date-time, and display a plurality of pastnotifications representing a plurality of past alerts from the pluralityof alerts, wherein the plurality of past alerts are associated withdate-times before the current date-time, and wherein the plurality ofpast alerts correspond to a first plurality of installed applications;detect a contact on the touch-sensitive display; determine whether thecontact is a tap or a substantially horizontal swipe; in response to adetermination that the contact is a substantially horizontal swipe:obtain a second current date-time, and display a plurality of futurenotifications representing a plurality of future alerts from theplurality of alerts, wherein the plurality of future alerts areassociated with date-times after the second current date-time, andwherein the plurality of future alerts correspond to a second pluralityof installed applications.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display cause the electronicdevice to: obtain a plurality of alerts associated with date-times;detect a first user input; in response to detecting the first userinput: obtain a first current date-time; display a plurality of futurenotifications representing a plurality of future alerts from theplurality of alerts, wherein the plurality of future alerts areassociated with date-times after the first current date-time, andwherein the plurality of future alerts correspond to a first pluralityof installed applications; detect a contact on the display; determinewhether the contact is a tap or a substantially horizontal swipe; inaccordance with a determination that the contact is a substantiallyhorizontal swipe: obtain a second current date-time; and display aplurality of past notifications representing a plurality of past alertsfrom the plurality of alerts, wherein the plurality of past alerts areassociated with date-times before the second current date-time, andwherein the plurality of past alerts correspond to a second plurality ofinstalled applications.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display cause the electronicdevice to: obtain a plurality of alerts associated with date-times;detect a first user input; in response to detecting the first userinput: obtain a first current date-time; display a plurality of futurenotifications representing a plurality of future alerts from theplurality of alerts, wherein the plurality of future alerts areassociated with date-times after the first current date-time, andwherein the plurality of future alerts correspond to a first pluralityof installed applications; detect a contact on the display; determinewhether the contact is a tap or a substantially horizontal swipe; inaccordance with a determination that the contact is a substantiallyhorizontal swipe: obtain a second current date-time; and display aplurality of past notifications representing a plurality of past alertsfrom the plurality of alerts, wherein the plurality of past alerts areassociated with date-times before the second current date-time, andwherein the plurality of past alerts correspond to a second plurality ofinstalled applications.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display and a rotatableinput mechanism cause the electronic device to: obtain a plurality ofalerts; display a first set of user interface objects; detect a rotationof the rotatable input mechanism; in response to detecting the rotation:determine whether the first set of user interface objects meets athreshold criteria; in accordance with a determination that the firstset of user interface objects meets the threshold criteria, replacedisplay of the first set of user interface objects with display of aplurality of notifications representing at least a subset of theplurality of alerts; and in accordance with a determination that thefirst set of user interface objects does not meet the thresholdcriteria, display a second set of user interface objects, wherein thesecond set is larger than the first set and comprises the first set.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display, the electronicdevice having an installed application, the electronic device configuredto communicate wirelessly with an external device, cause the electronicdevice to: receive application data associated with the installedapplication; display, on the touch-sensitive display of the electronicdevice, a first indication indicating receipt of the application data;receive a user's indication indicating whether the electronic device isto instruct the external device to display an indication indicatingreceipt, by the electronic device, of application data associated withthe installed application; and in response to the user's indication toinstruct the external device: send data to the external device, whereinthe data causes the external device to display a second indicationindicating receipt of the application data.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display cause the electronicdevice to: receive a plurality of alerts, wherein the alerts areassociated with date-times, wherein the alerts include content, andwherein the alerts correspond to a plurality of installed applications;detect a user input; and in response to detecting the user input,display a notification interface on the display, the notificationinterface comprising a plurality of notifications representing at leasta subset of the plurality of alerts, wherein the notifications aredisplayed in a chronological order based on the date-times associatedwith the alerts, and wherein the notifications include user interfaceobjects representative of the corresponding installed applications ofthe alerts, and wherein the notifications include at least a portion ofthe content of the plurality of alerts.

In some embodiments, an electronic device comprising a touch-sensitivedisplay can obtain a plurality of alerts associated with date-times. Thedevice can detect a user input, and in response to detecting the userinput, the device can obtain a current date-time and display anotification interface on the display, the notification interfacecomprising: a first notification representing a first alert of theplurality of alerts associated with a date-time after the currentdate-time, a second notification representing a second alert of theplurality of alerts associated with a date-time before the currentdate-time, and a graphical separator between the first notification andthe second notification, wherein the graphical separator comprises anindication of the current date-time, wherein the first alert and thesecond alert correspond to different installed applications.

In some embodiments, an electronic device comprising a touch-sensitivedisplay can obtain a plurality of alerts associated with date-times. Thedevice can detect a first user input, and in response to detecting thefirst user input, obtain a first current date-time and display aplurality of past notifications representing a plurality of past alertsfrom the plurality of alerts, wherein the plurality of past alerts areassociated with date-times before the current date-time, and wherein theplurality of past alerts correspond to a first plurality of installedapplications. The device can detect a contact on the touch-sensitivedisplay, and determine whether the contact is a tap or a substantiallyhorizontal swipe. In response to a determination that the contact is asubstantially horizontal swipe, the device can obtain a second currentdate-time, and display a plurality of future notifications representinga plurality of future alerts from the plurality of alerts, wherein theplurality of future alerts are associated with date-times after thesecond current date-time, and wherein the plurality of future alertscorrespond to a second plurality of installed applications.

In some embodiments, an electronic device comprising a touch-sensitivedisplay can obtain a plurality of alerts associated with date-times. Thedevice can detect a first user input, and in response to detecting thefirst user input, obtain a first current date-time and display aplurality of future notifications representing a plurality of futurealerts from the plurality of alerts, wherein the plurality of futurealerts are associated with date-times after the first current date-time,and wherein the plurality of future alerts correspond to a firstplurality of installed applications. The device can detect a contact onthe display, and determine whether the contact is a tap or asubstantially horizontal swipe. In accordance with a determination thatthe contact is a substantially horizontal swipe, the device can obtain asecond current date-time and display a plurality of past notificationsrepresenting a plurality of past alerts from the plurality of alerts,wherein the plurality of past alerts are associated with date-timesbefore the second current date-time, and wherein the plurality of pastalerts correspond to a second plurality of installed applications.

In some embodiments, an electronic device comprising a touch-sensitivedisplay can obtain a plurality of alerts associated with date-times. Thedevice can detect a first user input, and in response to detecting thefirst user input, obtain a first current date-time and display aplurality of past notifications representing a plurality of past alertsfrom the plurality of alerts, wherein the plurality of past alerts areassociated with date-times before the first current date-time, andwherein the plurality of past alerts correspond to a first plurality ofinstalled applications. The device can detect a contact on the display,and determine whether the contact is a tap or a substantially horizontalswipe. In accordance with a determination that the contact is asubstantially horizontal swipe, the device can obtain a second currentdate-time, and display a single future notification representing themost immediate upcoming alert in the plurality of alerts relative to thesecond current date-time.

In some embodiments, an electronic device comprising a touch-sensitivedisplay and a rotatable input mechanism can obtain a plurality ofalerts, and display a first set of user interface objects. The devicecan detect a rotation of the rotatable input mechanism, and in responseto detecting the rotation, the device can determine whether the firstset of user interface objects meets a threshold criteria. In accordancewith a determination that the first set of user interface objects meetsthe threshold criteria, the device can replace display of the first setof user interface objects with display of a plurality of notificationsrepresenting at least a subset of the plurality of alerts. In accordancewith a determination that the first set of user interface objects doesnot meet the threshold criteria, the device can display a second set ofuser interface objects, wherein the second set is larger than the firstset and comprises the first set.

In some embodiments, an electronic device comprising a touch-sensitivedisplay and having an installed application, where the electronic deviceis configured to communicate wirelessly with an external device, canreceive application data associated with the installed application. Thedevice can display, on the touch-sensitive display of the electronicdevice, a first indication indicating receipt of the application data.The device can receive a user's indication indicating whether theelectronic device is to instruct the external device to display anindication indicating receipt, by the electronic device, of applicationdata associated with the installed application. In response to theuser's indication to instruct the external device, the device can senddata to the external device, wherein the data causes the external deviceto display a second indication indicating receipt of the applicationdata.

In some embodiments, at an electronic device with a touch-sensitivedisplay can receive a plurality of alerts, where the alerts areassociated with date-times, include content, and correspond to aplurality of installed applications. The device can detect a user inputand, in response to detecting the user input, display a notificationinterface on the display. The notification interface can include aplurality of notifications representing at least a subset of theplurality of alerts, where the notifications are displayed in achronological order based on the date-times associated with the alerts.The notifications include user interface objects representative of thecorresponding installed applications of the alerts and include at leasta portion of the content of the plurality of alerts.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touchscreenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIG. 5C illustrates detection of contacts with intensity sensors.

FIG. 5D illustrates assigning an aggregate intensity to contacts.

FIGS. 5E-5H illustrate detection of a gesture having an intensity ofcontact.

FIGS. 6-21B illustrate exemplary user interfaces for displayingnotifications.

FIGS. 22-25 are flow diagrams illustrating exemplary processes fordisplaying a notification interface.

FIGS. 26-31 illustrate functional block diagrams in accordance with someembodiments.

FIG. 32 is a flow diagram illustrating an exemplary process fordisplaying a notification interface.

FIG. 33 illustrates a functional block diagram in accordance with someembodiments.

FIGS. 34-35 are flow diagrams illustrating exemplary processes fordisplaying a notification interface.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficientnotification interfaces to a user. For example, ease of use for viewingand managing notifications for alerts corresponding to a variety ofapplications can increase user efficiency. Such techniques can reducethe cognitive burden on a user who uses notifications, thereby enhancingproductivity. Further, such techniques can reduce processor and batterypower otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description ofexemplary devices for performing the techniques for managingnotifications. FIGS. 6-21B illustrate exemplary user interfaces fornotifications. The user interfaces in the figures are also used toillustrate the processes described below, including the processes inFIGS. 22-25, 32, and 34-35.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive displays 112 inaccordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience, and is sometimesknown as or called a touch-sensitive display system. Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure and the estimated force or pressure isused to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/or applicationspecific integrated circuits.

Memory 102 may include one or more computer-readable storage mediums.The computer-readable storage mediums may be tangible andnon-transitory. Memory 102 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 122 may control access tomemory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11nand/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161 and one or more input controllers 160 forother input or control devices. The one or more input controllers 160receive/send electrical signals from/to other input control devices 116.The other input control devices 116 optionally include physical buttons(e.g., push buttons, rocker buttons, etc.), dials, slider switches,joysticks, click wheels, and so forth. In some alternate embodiments,input controller(s) 160 are, optionally, coupled to any (or none) of thefollowing: a keyboard, an infrared port, a USB port, and a pointerdevice such as a mouse. The one or more buttons (e.g., 208, FIG. 2)optionally include an up/down button for volume control of speaker 111and/or microphone 113. The one or more buttons optionally include a pushbutton (e.g., 206, FIG. 2).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 and convertthe detected contact into interaction with user-interface objects (e.g.,one or more soft keys, icons, web pages or images) that are displayed ontouch screen 112. In an exemplary embodiment, a point of contact betweentouch screen 112 and the user corresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Patents: U.S. Pat. No. 6,323,846 (Westerman et al.), U.S.Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device, so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112 which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112 which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 2005/0190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.2006/0017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast or other visual property) of graphicsthat are displayed. As used herein, the term “graphics” includes anyobject that can be displayed to a user, including without limitationtext, web pages, icons (such as user-interface objects including softkeys), digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 may be used to manage an address book orcontact list (e.g., stored in application internal state 192 of contactsmodule 137 in memory 102 or memory 370), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 137, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 112 or on an external, connected display via external port124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions; data on stores and otherpoints of interest at or near a particular location; and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 152, FIG. 1A). In some embodiments, memory 102may store a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177 or GUI updater 178 to update the application internalstate 192. Alternatively, one or more of the application views 191include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) cardslot 210, headset jack 212, and docking/charging external port124. Push button 206 is, optionally, used to turn the power on/off onthe device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules may be combined or otherwise rearranged invarious embodiments. In some embodiments, memory 370 may store a subsetof the modules and data structures identified above. Furthermore, memory370 may store additional modules and data structures not describedabove.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 may optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touchscreen 504. Alternatively, or inaddition to touchscreen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touchscreen 504 (or the touch-sensitive surface) may haveone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors of touchscreen504 (or the touch-sensitive surface) can provide output data thatrepresents the intensity of touches. The user interface of device 500can respond to touches based on their intensity, meaning that touches ofdifferent intensities can invoke different user interface operations ondevice 500.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013 and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth™, nearfield communication (NFC), cellular and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 may be a rotatable input device or a depressible androtatable input device, for example. Input mechanism 508 may be abutton, in some examples.

Input mechanism 508 may be a microphone, in some examples. Personalelectronic device 500 can include various sensors, such as GPS sensor532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, and/or a combination thereof, all ofwhich can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 2200-2500 (FIGS. 22-25).The computer-executable instructions can also be stored and/ortransported within any non-transitory computer-readable storage mediumfor use by or in connection with an instruction execution system,apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. For purposes of this document, a“non-transitory computer-readable storage medium” can be any medium thatcan tangibly contain or store computer-executable instructions for useby or in connection with the instruction execution system, apparatus, ordevice. The non-transitory computer-readable storage medium can include,but is not limited to, magnetic, optical, and/or semiconductor storages.Examples of such storage include magnetic disks, optical discs based onCD, DVD, or Blu-ray technologies, as well as persistent solid-statememory such as flash, solid-state drives, and the like. Personalelectronic device 500 is not limited to the components and configurationof FIG. 5B, but can include other or additional components in multipleconfigurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example,an image (e.g., icon), a button, and text (e.g., hyperlink) may eachconstitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms mayeliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on a multifunctiondevice with a display and a touch-sensitive surface, such as devices100, 300, and/or 500, to improve a user's experience in viewing andmanaging alert notifications.

1. Notification User Interfaces

The current disclosure describes user interfaces for displaying multiplenotifications representing multiple alerts obtained by device 500.Device 500 can obtain alerts from installed applications running ondevice 500, or can obtain alerts from installed applications running onan external device that is in communication with device 500, forexample. In some embodiments, device 500 obtains alerts by receiving thealerts from an application or an external device.

In some embodiments, an alert can be a text message, calendar alert,voicemail, clock alarm, system alert, weather alert, email, or fitnessalert, for example. An alert may be associated with a date and a time,referred to as a “date-time,” that characterizes the date and time thealert was sent or received, or the date and time of an upcoming alertevent, for example. An alert date-time may be a future (e.g., upcoming)date-time or a past date-time, relative to the current date and time. Analert date-time may be a timestamp assigned to the alert by device 500or by an external device, or may be a date and time assigned within anapplication (e.g., a date and time associated with a calendar reminderor clock alarm). An alert may be a timeless alert; that is, an alertthat is not associated with a specific date-time, such as a taskreminder or location-based alert that is triggered when device 500 is ina specific location, or within a predefined geofence.

A received alert may include information, such as a source of the alert,an application corresponding to the alert, a date-time, and alertcontent. The alert content may be the body of a text message, avoicemail message, an image, or text associated with a calendarreminder, for example. A notification representing an alert may includeat least a portion of the alert information.

The notification user interfaces described below are illustrated by wayof exemplary sequences of screens that device 500 can display afterreceiving multiple alerts and detecting various user inputs. In thesesequences, the arrows indicate the order in which the screens aredisplayed.

a. Future and Past Notifications on Single Screen

In some embodiments, device 500 can display multiple future and pastnotifications in a single notification interface screen. For example,FIG. 6 depicts a sequence of screens that device 500 can display ontouchscreen 504 after receiving multiple alerts. Initially, in someembodiments, home screen 602 is displayed on touchscreen 504. Homescreen 602 may include a plurality of user interface objects 604associated with a plurality of applications, services, or otherfunctions that may be launched from home screen 602. In someembodiments, home screen 602 includes a clock face.

In response to detecting a contact on touchscreen 504, device 500 candetermine a current date-time and display notification interface screen606. In some embodiments, the contact is a substantially vertical swipe,such as a downward swipe, or flick on touchscreen 504. In someembodiments, the contact is a touch or tap on a user interface object604 displayed on home screen 602.

Notification interface screen 606 includes multiple future notifications608 that represent alerts associated with date-times that are after thecurrent date-time. Notification interface screen 606 also includesmultiple past notifications 610 that represent alerts that areassociated with date-times that are before the current date-time.

Notification interface screen 606 also includes a graphical separator616. In some embodiments, a graphical separator may be a contiguous,predefined area of the display used to separate some notifications fromother notifications. In some embodiments, the graphical separatorcomprises an indication of the current time 618, and is displayedbetween the future notifications (e.g., 608) and past notifications(e.g., 610) as depicted in FIG. 6.

In some embodiments, each notification 608, 610 corresponds to a singlealert received by device 500. As will be discussed with respect to FIG.14, in some embodiments, multiple alerts may be represented by a singlegrouped notification in a notification interface screen.

In the example depicted in FIG. 6, past notifications and futurenotifications are displayed chronologically, such that the mostimmediate upcoming alert is represented by a future notification that isimmediately above the graphical separator, and the most recent pastalert is represented by a past notification that is immediately belowthe graphical separator. Future notifications that are displayed fartherabove the graphical separator are associated with date times that arefarther in the future; past notifications that are displayed fartherbelow the graphical separator are associated with date times that arefarther in the past. In some embodiments, notifications are displayed inother orders, as will be discussed in more detail with respect to FIGS.19-21.

In some embodiments, a notification 608, 610 includes an applicationaffordance 612, 614 for launching an application that corresponds to thealert represented by the notification. In some embodiments, launchingthe application corresponding to the alert causes the application to bedisplayed on touchscreen 504, and may include opening the alert withinthe application for viewing, editing, or responding to the alert. Insome embodiments, if the alert is a text message, launching theapplication displays a text message conversation that includes the textmessage. For example, as depicted in FIG. 7, in response to detecting acontact on application affordance 614, device 500 launches the textmessage application and displays a conversation that includes the textmessage. The contact may be a touch or tap on application affordance614, for example.

As depicted in FIG. 8, in some embodiments, in response to detecting auser input, device 500 scrolls the notification interface (includinggraphical separator 616) to display additional future notifications 608or past notifications 610. In some embodiments, the user input is avertical swipe or flick on touchscreen 504, such as indicated in FIG. 8.In some embodiments, device 500 scrolls notification interface screen606 in the same direction as the swipe or flick.

As depicted in FIG. 8, in some embodiments, if graphical separator 616is scrolled in a direction (e.g., up or down) to a boundary oftouchscreen 504, such as the top or bottom of touchscreen 504, device100 can cease to scroll graphical separator 616 and continue to displaygraphical separator 616 at the boundary of touchscreen 104 whilecontinuing to scroll the notifications 608, 610 in the same direction.Thus, the graphical separator may “stick” to the top or bottom of thescreen while device 100 continues to scroll the notifications in thesame direction. In response to detecting a user input for scrolling inthe opposite direction, such as a swipe or flick in the oppositedirection, device 100 can scroll the notification interface inaccordance with the user input, and resume scrolling the graphicalseparator away from the boundary of touchscreen 504 so that it continuesto provide a visible separation between past and future notificationsand, optionally, additional useful information such as a time of day.Moreover, the location of the graphical separator provides a visual cueas to whether the currently displayed notifications are pastnotifications (e.g., if the graphical separator is at or near the top ofthe display) or future notifications (e.g., if the graphical separatoris at or near the bottom of the display).

As depicted in FIG. 8, in some embodiments, if notification interface606 has been scrolled out of its initial position, then device 500 canrefresh notification interface 606 in response to detecting a contact ongraphical separator 616. In some embodiments, device 500 can refreshnotification interface screen 606 by re-displaying notificationinterface screen 606 in its initial, un-scrolled position. In someembodiments, when notification interface screen 606 is refreshed, device500 determines a new current date-time and updates the display positionsof notifications 608, 610 based on the new current date-time. Forexample, one or more future notifications may have become pastnotifications if their associated date-times have passed whennotification interface is refreshed, such that they are displayed on thesame side of the graphical separator as the other past notifications.

A user may wish to dismiss a notification from a notification interfaceso that it is no longer displayed in the notification interface. Asdepicted in FIG. 9, in some embodiments, if device 500 detects a contacton a notification 610 that meets a dismissal criteria, then device 500dismisses notification 610. In some embodiments, a dismissednotification is excluded from subsequent notification interfacesdisplayed by device 500.

In some embodiments, the contact meets the dismissal criteria if it is ahorizontal swipe or flick on the notification. In some embodiments, thecontact meets the dismissal criteria if the distance of the swipe orflick across the touchscreen exceeds a threshold distance. In someembodiments, the threshold distance is a quarter, half, or ¾ of thehorizontal width of touchscreen 504.

Returning to FIG. 9, in some embodiments, in response to detecting amovement of a contact (such as a horizontal swipe) on touchscreen 504 ata location corresponding to notification 610, device 500 can slidenotification 610 on the touchscreen in the direction of the movement ofthe contact and display a dismissal indicator 902 adjacent to thenotification. The dismissal indicator 902 may provide the user with avisual cue that, if the movement of the contact is continued in the samedirection, the notification will be dismissed. After displaying thedismissal indicator, in some embodiments, if the contact meets thethreshold criteria, then in response to detecting the release of thecontact, device 500 can dismiss notification 610, remove the dismissalindicator 902 from touchscreen 504, and re-display the notificationinterface 606 excluding the dismissed notification 610. If the contactdoes not meet the threshold criteria (for example, if the movement ofthe contact does not exceed a threshold distance), device 500 candisplay an animation that slides notification 610 back to its initialposition on the display, and remove the dismissal indicator 902 from thedisplay. In some embodiments, dismissing notification 610 involvesdisplaying an animation that slides notification 610 off of touchscreen504 in the direction of the swipe or flick.

In some cases, a user may wish to dismiss more than one notification ata time from a notification interface. As depicted in FIG. 10, inresponse to detecting a contact on touchscreen 504 while displayingnotification interface 606, device 500 can determine whether thecharacteristic intensity of the contact exceeds a threshold intensity.If the characteristic intensity exceeds the threshold intensity (forexample, if the contact is a hard push on touchscreen 504), the device500 can display affordance 1002 for dismissing multiple notificationsfrom the notification interface. In some embodiments, device 500 candisplay affordance 1002 in response to detecting a liftoff of a contacthaving a characteristic intensity that exceeds a threshold intensity.

In some embodiments, the response to the contact may belocation-independent; that is, a contact anywhere on touchscreen 504that has a characteristic intensity above a threshold intensity maycause device 500 to display affordance 1002. In contrast, if thecharacteristic intensity of the contact is below the thresholdintensity, device 500 can respond in a different manner. For example, ifthe contact is detected on a displayed notification, and thecharacteristic intensity is below the threshold intensity (e.g., thecontact is a touch or tap on a notification, where the contact does nothave a characteristic intensity above the threshold intensity during thetouch or tap), device 500 can respond by displaying alert content, asdescribed below with respect to FIG. 11A.

In some embodiments, displaying affordance 1002 involves replacingdisplay of notification interface screen 606 with display of affordance1002. In some embodiments, displaying affordance 1002 involvesdisplaying affordance 1002 overlaid on notification interface screen606.

In some embodiments, in response to detecting a selection of affordance1002, device 500 can dismiss all of the notifications that are includedin the notification interface. In some embodiments, in response todetecting a selection of affordance 1002, device 500 can dismiss somesubset of the notifications, such as the past notifications or futurenotifications.

As previously discussed, an alert may include alert content, such as thebody of a text message or email, an audio message, or additional alertdetails. As depicted in FIG. 11A, in some embodiments, in response todetecting a contact on a notification 1104 representing an alert innotification interface screen 1102, device 500 can replace display ofnotification interface screen 1102 with alert details screen 1106, whichincludes some or all of the alert content. The contact may be a touch ortap on notification 1104, for example. In some embodiments, device 500can display alert details screen 1106 in response to detecting a liftoffof the contact. In some embodiments, alert details screen 1106 includesapplication affordance 1108 which, when selected, can launch theapplication corresponding to the alert.

As depicted in FIG. 11B, in some embodiments, after displaying alertdetails screen 1106, device 500 can exclude notification 1104 fromsubsequently displayed notification interface screen 1110.

b. Next-Up Notification and Past Notifications on Single Screen

FIG. 12 depicts another exemplary sequence of screens that device 500can display on touchscreen 504 after receiving multiple alerts anddetecting a user input invoking a notification interface, as describedwith respect to FIG. 6. This sequence is similar to the sequencedepicted in FIG. 6, however, instead of the notification interfacedisplaying multiple future notifications, notification interface screen1206 displays a single, “next up” notification 1208 above graphicalseparator 1216 and multiple past notifications 1210 below graphicalseparator 1216. In some embodiments, the “next up” notification 1210 isthe next immediate upcoming alert, based on the current date-time. Aswith the previous example, past notifications 1210 in notificationinterface screen 1206 represent alerts having date-times that are in thepast relative to the current date and time.

Graphical separator 1216 of notification interface screen 1206 does notinclude an indication of the current time. However, notificationinterface screen 1206 includes an indication of the current time 1218displayed at the top of notification interface screen 1206.

Notification interface screen 1206 can be scrolled to display additionalpast notifications. Device 500 can scroll notification interface screen1206 in response to user inputs as described with respect to FIG. 6. Forexample, in response to detecting an upward swipe or flick ontouchscreen 504, device 500 can scroll notification interface screen1206 to display additional past notifications. However, in exemplarynotification interface 1206, graphical separator 1216 does not “stick”to a boundary of touchscreen 504. In response to detecting a contact onthe indication of the current time 1218, device 500 can re-displaynotification interface screen 1206 in its initial, un-scrolled position,as previously described.

c. Future and Past Notifications on Separate Screens

In some embodiments, device 500 can display a notification interfacewith future notifications on one screen and past notifications onanother screen. For example, FIG. 13 depicts a sequence of screens thatdevice 500 can display on touchscreen 504 when a notification interfaceis invoked as described with respect to FIG. 6.

In response to detecting a user input to invoke the notificationinterface from home screen 602, device 500 can display notificationinterface screen 1306. Notification interface screen 1306 includesmultiple past notifications 1310 representing past alerts. In someembodiments, the past notifications 1310 are displayed in achronological order, starting with the most recently passed pastnotification.

In response to detecting a contact on touchscreen 504 while displayingnotification interface screen 1306, device 500 can replace display ofnotification interface screen 1306 with display of notificationinterface screen 1312. In some embodiments, the contact is a horizontalswipe or flick on touchscreen 504, such as a right to left swipe orflick.

In some embodiments, replacing display of notification interface screen1306 with notification interface screen 1312 involves horizontallytranslating notification interface screen 1306 off of touchscreen 504 onone side while horizontally translating notification interface screen1312 onto touchscreen 504 from the other side, such that portions ofboth screens are simultaneously visible during the transition from onescreen to another.

Notification interface screen 1312 displays multiple futurenotifications 1308 representing future alerts. The future notificationsare displayed in a chronological order, starting with the mostimmediately upcoming notification. In this example, notificationinterface screen 1312 also includes a timeless notification 1314 thatrepresents an alert that is not associated with a date-time. In someembodiments, timeless notifications are displayed with the pastnotifications instead of with the future notifications.

In some embodiments, notification interface screens 1306, 1312 do notinclude a graphical separator, because past and future notifications arenot displayed on the same screen in the same manner as in, for example,notification interface screen 606.

In the example of FIG. 13, notification interface screens 1306 and 1312include page indicators 1304 to provide a visual indication to the userof the number and relative position of additional screens that may bedisplayed in response to horizontal contacts. For example, the leftmostpage indicator of screen 1306 is solidly filled and the page indicatoradjacent to it is not filled, suggesting that a left horizontal swipemay display another screen (e.g., screen 1312).

d. Missed Notifications, Up Next, and Activity on Separate Screens

In some embodiments, device 500 can display a notification interfacewith past notifications on a first screen, a single “Up Next”notification on a second screen, and a summary of user physical activityon a third screen. For example, FIG. 14 depicts a sequence of screensthat device 500 can display on touchscreen 504 when a notificationinterface is invoked as described with respect to FIG. 6.

In response to detecting a user input to invoke a notificationinterface, device 500 can display notification interface screen 1402.Notification interface screen includes notifications representingmultiple past alerts. However, in this example, rather than displayingmultiple past notifications that each represent a single past alert asdepicted in FIG. 6 (for example), notification interface screen 1402aggregates the notifications into multiple grouped past notifications1404, 1406, where each grouped notification represents multiple pastalerts that correspond to the same application. For example, groupednotification 1404 represents two past text message alerts, while groupednotification 1406 represents three past email alerts. In someembodiments, grouped notifications can include an application affordance1410, 1412 for launching an application corresponding to the alertsrepresented by the grouped notification. In some embodiments, launchingthe application opens the application and displays the application inboxwith a list of the alerts represented by the grouped notification. Insome embodiments, the alerts represented by grouped notifications 1404,1404 in notification interface screen 1402 are alerts that were missed.In some embodiments, a missed alert is an alert for which the associatedcontent has not been displayed, or that was received when touchscreen504 was dark or inactive.

In response to detecting a contact on touchscreen 504 while displayingnotification interface screen 1402, device 500 can replace display ofnotification interface screen 1402 with display of notificationinterface screen 1414. In some embodiments, the contact is a horizontalswipe or flick on touchscreen 504, such as a swipe or flick from rightto left on touchscreen 504.

As previously discussed with respect to FIG. 13, in some embodiments,replacing display of notification interface screen 1402 withnotification interface screen 1414 involves horizontally translatingnotification interface screen 1402 off of touchscreen 504 on one sidewhile horizontally translating notification interface screen 1414 ontotouchscreen 504 from the other side, such that portions of both screensare simultaneously visible during the transition from one screen toanother.

In some embodiments, notification interface screen 1414 includes anup-next notification 1416 representing the most immediate future alert.In some embodiments, the up-next notification 1416 includes anapplication affordance 1418 for launching an application correspondingto the alert represented by up-next notification 1416. In someembodiments, notification interface screen 1414 provides the user with aquick snapshot of their next upcoming event or activity.

The up-next notification can represent a variety of alerts thatcorrespond to different applications. For example, an up-nextnotification could be a calendar alert, a bus departure time, or anairline boarding gate (provided by a travel application, for example).Such alerts may be received from an external electronic device or froman installed application executing on device 500.

FIGS. 15A-D depict exemplary up-next notifications representing alertsthat correspond to different applications. FIG. 15A depicts an up-nextnotification representing an alert that may correspond to a calendarapplication. FIG. 15B depicts an up-next notification representing analert that may correspond to restaurant reservation application. FIGS.15C-D depict up-next notifications that may correspond to an airlinetravel application.

In some embodiments, as depicted in FIG. 16, an up-next notification isupdated in accordance with information received from an applicationcorresponding to the alert represented by the notification. In theexample of FIG. 16, the corresponding application may be a travelreservation application. As another example, the correspondingapplication is a calendar application, and the information may be anappointment or a reminder to depart at a certain time to arrive at yournext calendar appointment. In some examples, an up-next notificationincludes an affordance to launch an application, such as a mapapplication, which may be pre-populated with an address to which device500 has determined that a user is likely to be navigating (based oninformation obtained from a calendar application, for example).

Returning to FIG. 14, in some embodiments, in response to detecting acontact on touchscreen 504 while displaying notification interfacescreen 1414, device 500 can replace display of notification interfacescreen 1414 with display of notification interface screen 1422. In someembodiments, the contact is a horizontal swipe or flick on touchscreen504, such as a swipe or flick from right to left on touchscreen 504.Notification interface screen 1422 includes an indication of userphysical activity status 1428. In this example, the user physicalactivity status includes the number of steps the user has taken over atime period, the amount of time the user has been active over the timeperiod, and the amount of time a user has been sitting over the timeperiod. More generally, the indication of activity status may includespecific actions, such as exercise duration, sleeping duration,sitting/sedentary duration, elevation or distance traversed. In someembodiments, the indication of activity status may include informationbased on sensor data, such as heart rate, blood pressure, ortemperature. In some examples, the activity status is reset at thebeginning of each hour, day, week, month, or user-specified time period,for example. Techniques for monitoring a user's physical activities aredescribed in co-pending U.S. Provisional Patent Application Ser. No.62/044,990 entitled “Physical Activity and Workout Monitor,” filed Sep.2, 2014 and U.S. Provisional Patent Application Ser. No. 62/129,828entitled “Physical Activity and Workout Monitor,” filed Mar. 7, 2015,both of which are herein incorporated by reference in their entirety.

Notification interface screens 1402, 1414, and 1422 include pageindicators 1424, as previously described with respect to FIG. 13. Insome embodiments, device 500 can horizontally scroll betweennotification interface screen 1402, notification interface screen 1414,and notification interface screen 1422 in response to horizontal swipesor flicks on touchscreen 504. A person of skill in the art willrecognize that the screen order depicted in FIG. 14 is only one possiblearrangement; other orders are also possible. For example, in response todetecting a user input to invoke a notification interface, device 500can display notification interface screen 1414 first, and then scroll toscreens 1402 and 1422 in response to horizontal swipes on touchscreen504.

More generally, a person of skill in the art will recognize that theexemplary notification interface screens described with respect to FIGS.6-16 can be combined in many different ways to create differentnotification interfaces. For example, a notification interface screenfrom one example notification interface may be replaced by anotification interface screen from another example without departingfrom the scope of this disclosure. While the examples described hereindepict up to three notification interface screens in a notificationinterface, in some embodiments, a notification interface may includefour or more screens, each with different information. For example, anotification interface may include an “up next” screen, a futurenotifications screen, a past notifications screen (with grouped orungrouped notifications), and an activity screen.

2. Invoking Notification Interfaces

As previously discussed with respect to FIGS. 6-16, device 500 candisplay a notification interface screen in response to detecting acontact on touchscreen 104. FIGS. 6-16 depict the contact as a downwardswipe on touchscreen 504. In some embodiments, device 500 can display anotification interface screen in response to detecting an upward swipeor a horizontal swipe.

As depicted in FIG. 17, in some embodiments, device 500 can display anotification interface screen in response to a touch or tap on anotification affordance 1704 on home screen 1702. In some embodiments,notification affordance 1704 includes an indication 1706 of the numberof unread alerts received since a notification interface was lastdisplayed.

In some embodiments, device 500 can zoom in or out of a notificationinterface screen in response to detecting a touch on touchscreen 504 anddetecting a rotation of the rotatable input mechanism. In someembodiments, device 500 can zoom the notification interface screen ifthe touch and at least a portion of the rotation are detectedessentially simultaneously. For example, device 500 may detect a usercontact on touchscreen 504, and detect a rotation of the rotatable inputmechanism while the touch continues to be detected. In some embodiments,device 500 can zoom in a notification interface (e.g., display contentat a larger size) in response to detecting the rotation in a firstdirection, and zoom out the notification interface (e.g., displaycontent at a smaller size) in response to detecting a rotation in theopposite direction.

As depicted in FIG. 18, in some embodiments, device 500 can display anotification interface screen in response to detecting a rotation of arotatable input mechanism 508. While displaying home screen 602 with afirst set of user interface objects 604, in response to detecting aninitial rotation of rotatable input mechanism 508, device 500 can zoomout home screen 602 to display home screen 1802 with a second set ofapplication affordances 1804, where the second set has more userinterface objects than the first set and includes the first set. If homescreen 602 is already zoomed out to its maximum zoom-out level, inresponse to detecting a further rotation of the rotatable input device,device 500 can display notification interface screen 1806 (or anotheruser interface screen, as described above). In some embodiments, device500 can determine whether home screen 602 is already zoomed out to itmaximum zoom-out level if the first set of user interface objects 604meets a threshold criteria. The threshold criteria may be based on thenumber of user interface objects displayed, the display size of the userinterface objects, and/or whether all of the installed applications arerepresented by the displayed user interface objects.

3. Notification Display Order

As previously discussed, notifications displayed in a notificationinterface may be displayed in a chronological order by the date-times ofthe associated alerts. FIG. 19A depicts notification interface screen1902 with notifications 1906-1918 displayed in chronological order basedon the associated date-times of the alerts represented by thenotifications. In this example, the notifications 1906-1918 are pastnotifications; they represent text messages, emails, and alertspreviously received. (Text messages, emails, and voicemails are pastalerts since they are received before the current date-time.)

For simplicity, exemplary notification interface screen 1902 does notinclude a graphical separator; screen 1902 is intended to primarilydepict notification display order, rather than depicting a particularnotification interface.

As depicted in FIG. 19A, in some embodiments, device 500 can display oneor more timeless notifications 1904 representing timeless alerts thatare not associated with a particular date-time, such as task remindersor location-based alerts (e.g., alerts that are received based on alocation of device 500, such as store coupons), at the top of thenotifications.

FIG. 19B depicts an alternative exemplary notification interface screen1920 with past notifications 1934, 1936, and 1938 displayed inchronological order based on the associated date-times of the alertsrepresented by the notifications. Notifications 1934, 1936, and 1938correspond respectively to the same alerts as notifications 1914, 1916,and 1918 on notification interface screen 1902 depicted in FIG. 19A. Incontrast to notification interface screen 1902, notification interfacescreen 1920 does not include a timeless notification corresponding totimeless notification 1904. Also, notifications associated withdate-times further in the past are displayed above more recentnotifications. That is, the notifications are in reverse chronologicalorder compared to notification interface screen 1902. In someembodiments, the notifications are displayed in the style illustrated innotification interface screen 1920, but in the same chronological orderas the notifications in notification interface screen 1902.

Notification interface screen 1920 also displays notifications in adifferent format, or style, than notification interface screen 1902. Forexample, in notification interface screen 1920, the notificationsinclude a textual descriptor (e.g., 1940) of the application thatcorresponds to the alert represented by the notification, andnotifications of emails (e.g., 1936) include at least a portion of thesubject (e.g., 1941) and the body (e.g., 1942) of the email.

In some embodiments, a notification s 1934, 1936, and 1938 includeapplication affordances 1943, 1944, and 1945, respectively, forlaunching an application that corresponds to the alert represented bythe notification, as described above with reference to FIGS. 6-7.

In some embodiments, notifications of more recent alerts can bedisplayed in response to a user input. Device 500 can scrollnotification interface screen 1920 in response to user inputs asdescribed with respect to notification interface screen 606 and FIG. 8.For example, in response to detecting a rotation of rotatable inputmechanism 508 or an upward swipe, drag, or flick on touchscreen 504,device 500 can scroll notification interface screen 1920 to displayadditional past notifications of more recent alerts. As depicted in FIG.19C, in some embodiments, in response to detecting a vertical swipe,drag, or flick on touchscreen 504 (such as indicated in FIG. 19B),device 500 scrolls notification interface screen 1920 in the samedirection as the swipe, drag, or flick. That is, device 500 scrollsnotification interface screen 1920 upward to display additional pastnotifications 1926, 1928, 1930, and 1932, which correspond respectivelyto the same alerts as notifications 1906, 1908, 1910, and 1912 onnotification interface screen 1902 depicted in FIG. 19A.

In some embodiments, in response to the same user input that causesscrolling, device 500 displays an indication based on the currentlydisplayed notifications relative to the entire set of notificationsassociated with notification interface screen 1920. For example, device500 can display an exemplary indicator 1950 as depicted in FIG. 19C. Insome embodiments, indicator 1950 is displayed over at least a portion ofone or more notifications. In the embodiment shown in FIG. 19C,indicator 1950 includes translucent user interface object 1952, which isdisplayed over a portion of notification 1930. Translucent userinterface object 1952 is representative of the extent of notificationinterface screen 1950 (e.g., the size and/or number of notifications1926-1938).

Indicator 1950 also includes an opaque user interface object 1954overlaid on translucent user interface object 1952. The size andlocation of user interface object 1954 relative to translucent userinterface object 1952 is representative of the position of the currentlydisplayed notifications (e.g., notifications 1926, 1928, 1930, and 1932in FIG. 19C) relative to the entire set of notifications associated withnotification interface screen 1920 (e.g., notifications 1926-1938). Insome embodiments, indicator 1950 is representative of a proportion ofthe entire set of notifications that are currently displayed. Forexample, the size of opaque user interface object 1954 relative to thesize of translucent user interface object 1952 represents the proportionof the notifications that are currently displayed.

In some embodiments, indicator 1950 is displayed in a fixed location. Insome embodiments, indicator 1950 is displayed adjacent to rotatableinput mechanism 508. In some embodiments, device 500 ceases to displayindicator 1950 in accordance with a predetermined amount of time ofinactivity after the input that causes scrolling. In some embodiments,device 500 ceases to display indicator 1950 by fading out indicator 1952over time.

In some embodiments, device 500 can display notifications in ordersother than strictly chronological. In some embodiments, device 500 candisplay notifications in an order based on any combination of chronology(e.g., date-time), the application associated with the alert, and thealert source.

For example, FIG. 20A depicts a notification interface screen 2002 thatincludes the same set of notifications as depicted in FIG. 19. However,in notification interface screen 2002, the notifications are grouped byapplication, and are displayed chronologically within each applicationgrouping. For example, all of the notifications representing textmessages are displayed in notification group 2006, and arechronologically displayed within the group. As in FIG. 19A, the timelessnotification 1904 is displayed at the top of the notification interface.In this example, the application grouping that includes the most recentnotification is displayed closest to the top.

FIG. 20B depicts yet another notification interface screen 2004 thatincludes the same set of notifications depicted in FIG. 19. However, innotification interface screen 2004, the notifications are grouped firstby the application associated with the alerts, then by the source of thealerts, then chronologically. In this example, the application groupingthat includes the most recent notification is displayed closest to thetop.

FIG. 21A depicts yet another notification interface screen 2102 thatincludes the same set of notifications depicted in FIG. 19. However, innotification interface screen 2102, the notifications are grouped by thealert source (e.g., Jon Daly, NYT), and then displayed chronologicallyfor each source. In this example, the source group with the most recentnotification is displayed at the top of the notifications.

FIG. 21B depicts yet another notification interface screen 2104 thatincludes the same set of notifications depicted in FIG. 19. As in FIG.21A, the notifications are grouped by alert source, but in this example,they are also grouped by application within the source grouping. Withina given source grouping, the application group with the most recentnotification is displayed at the top of the source grouping, and thesource grouping with the most recent notification is displayed at thetop of the notifications.

A person of skill in the art will recognize that many alternativegroupings and orderings are possible, based on various informationassociated with the received alerts. Although FIGS. 19-21 depictnotification interface screens that include past notifications, similarorderings may be used for display of future notifications. In someembodiments, device 500 can display future notifications in one order,and past notifications in a different order.

4. Alerts Received from External Device

As previously discussed, device 500 can obtain alerts from installedapplications running on device 500, or can receive alerts from installedapplications running on an external device that is in communication withdevice 500. In the latter case, the external device may be configured bya user to instruct device 500 to display notifications representing thealerts.

In some embodiments, the external device may display notificationinterfaces that are different from or similar to those described above.In some embodiments, the external device may be configured to suppresssending alerts to device 500 for one or more applications. In this case,a notification interface displayed on the external device may includealert notifications that are not included in a notification interfacedisplayed on device 500. Techniques for configuring a device to forwardnotifications from one device to another are described in co-pendingU.S. Provisional Patent Application entitled “Coordination of MessageAlert Presentations Across Devices Based on Device Modes,” filed Sep. 2,2014 and naming James Cary as inventor, and U.S. Provisional PatentApplication entitled “Message Processing By Subscriber App Prior ToMessage Forwarding,” filed Sep. 2, 2014 and naming James Cary asinventor.

5. Methods for Managing Notification Interfaces

FIG. 22 is a flow diagram illustrating a method for displaying andmanaging notifications using an electronic device in accordance withsome embodiments. Method 2200 may be performed at an electronic devicewith a touch-sensitive display screen, such as device 100, 300 and/or500 (FIGS. 1, 3, 5, and 26). Some operations in method 2200 may becombined, the order of some operations may be changed, and someoperations may be omitted.

As described below, method 2200 provides an intuitive way for displayingand managing alert notifications. The method reduces the cognitiveburden on a user by reducing the number of inputs required to displayinformation of interest to a user. For battery-operated computingdevices, enabling a user to display and manage alert notificationsfaster and more efficiently conserves power and increase the timebetween battery charges.

At block 2202, the device obtains a plurality of alerts associated withdate-times. At block 2204, the device detects a user input. In someembodiments, the user input may be a touch, tap, or swipe on thetouchscreen (e.g., 112, 355, 504). In some embodiments, the user inputmay be a rotation of a rotatable input mechanism (e.g., 506). At block2206, in response to detecting the user input, the device obtains acurrent date-time and displays a notification interface (as depicted in,for example, FIG. 6). The notification interface includes a firstnotification (e.g., 610) representing a first alert that is associatedwith a date-time before the current date-time, a second notification(e.g., 608) representing a second alert associated with a date-timeafter the current date-time, and a graphical separator (e.g., 616)between the first notification and the second notification. The firstalert and second alert correspond to different installed applications.

Optionally, the device detects a second user input. In some embodiments,the user input may be a touch, tap, or swipe on the touchscreen (e.g.,112, 355, 504). In some embodiments, the user input may be a rotation ofa rotatable input mechanism (e.g., 506). In response to detecting thesecond user input, the device scrolls the notification interface inaccordance with the second user input (as depicted in, for example, FIG.8).

Optionally, if the graphical separator (e.g., 616) is scrolled to aboundary of the touchscreen, the device can cease to scroll thegraphical separator while continuing to scroll the additionalnotifications in accordance with the second input (as depicted in, forexample, FIG. 6).

Note that details of the processes described above with respect tomethod 2200 (e.g., FIGS. 22, 6, and 8) are also applicable in ananalogous manner to the other methods described herein. For example,methods 2300, 2400, 2500, 3200, 3400, and 3500 may include one or moreof the characteristics of the various methods described above withreference to method 2200. For brevity, these details are not repeated inthe descriptions of the other processes. The various methods andtechniques described above with reference to method 2200 may beoptionally implemented as one or more hardware units, such as thosedescribed with regard to FIGS. 5B and 26.

FIG. 23 is a flow diagram illustrating a method for displaying andmanaging notifications using an electronic device in accordance withsome embodiments. Method 2300 may be performed at an electronic devicewith a touch-sensitive display screen, such as device 100, 300 and/or500 (FIGS. 1, 3, 5, and 27). Some operations in method 2300 may becombined, the order of some operations may be changed, and someoperations may be omitted.

As described below, method 2300 provides an intuitive way for displayingand managing alert notifications, by providing an intuitiverepresentation of received alerts. The method reduces the cognitiveburden on a user by reducing the number of inputs required to displayinformation of interest to a user. For battery-operated computingdevices, enabling a user to display and manage alert notificationsfaster and more efficiently conserves power and increase the timebetween battery charges.

At block 2302, the device obtains a plurality of alerts associated withdate-times. At block 2304, the device detects a user input. In someembodiments, the user input may be a touch, tap, or swipe on thetouchscreen (e.g., 112, 355, 504). In some embodiments, the user inputmay be a rotation of a rotatable input mechanism (e.g., 506). At block2306, in response to detecting the user input, the device obtains acurrent date-time, and displays a plurality of past notifications (e.g.,1310) representing a plurality of past alerts associated with date-timesbefore the current date-time (as depicted in FIG. 13, for example). Theplurality of past alerts correspond to a first plurality of installedapplications. At block 2308, the device detects a contact on thetouchscreen (e.g., 112, 355, 504). At block 2310, the device determineswhether the contact was a tap or a substantially horizontal swipe. Atblock 2312, in accordance with a determination that the contact was asubstantially horizontal swipe, the device displays a plurality offuture notifications (e.g., 1308) representing a plurality of futurealerts associated with date-times after the current date-time (asdepicted in FIG. 13, for example). The plurality of future alertscorrespond to a second plurality of installed applications.

Note that details of the processes described above with respect tomethod 2300 (e.g., FIGS. 23 and 13) are also applicable in an analogousmanner to the other methods described herein. For example, methods 2200,2400, 2500, 3200, 3400, and 3500 may include one or more of thecharacteristics of the various methods described above with reference tomethod 2300. For brevity, these details are not repeated in thedescriptions of the other methods. The various methods and techniquesdescribed above with reference to method 2300 may be optionallyimplemented as one or more hardware units, such as those described withregard to FIGS. 5B and 27.

FIG. 24 is a flow diagram illustrating a method for displaying andmanaging notifications using an electronic device in accordance withsome embodiments. Method 2400 may be performed at an electronic devicewith a touch-sensitive display screen, such as device 100, 300 and/or500 (FIGS. 1, 3, 5, and 29). Some operations in method 2400 may becombined, the order of some operations may be changed, and someoperations may be omitted.

As described below, method 2400 provides an intuitive way for displayingand managing alert notifications, by providing an intuitiverepresentation of received alerts. The method reduces the cognitiveburden on a user by reducing the number of inputs required to displayinformation of interest to a user. For battery-operated computingdevices, enabling a user to display and manage alert notificationsfaster and more efficiently conserves power and increase the timebetween battery charges.

At block 2402, the device obtains a plurality of alerts associated withdate-times. At block 2404, the device detects a user input. In someembodiments, the user input may be a touch, tap, or swipe on thetouchscreen (e.g., 112, 355, 504). In some embodiments, the user inputmay be a rotation of a rotatable input mechanism (e.g., 506). At block2406, in response to detecting the user input, the device obtains afirst current date-time, and displays a plurality of past notifications(e.g., 1404, 1406) representing a plurality of past alerts associatedwith date-times before the first current date-time, as depicted in FIG.14, for example. The plurality of past alerts correspond to a firstplurality of installed applications. At block 2408, the device detects acontact on the touchscreen (e.g., 112, 355, 504). At block 2410, thedevice determines whether the contact was a tap or a substantiallyhorizontal swipe. At block 2412, in accordance with a determination thatthe contact was a substantially horizontal swipe, the device displays asingle future notification (e.g., 1416, FIG. 15A-15D, FIG. 16)representing the most immediate upcoming alert relative to the secondcurrent date-time.

Note that details of the processes described above with respect tomethod 2400 (e.g., FIGS. 24 and 14) are also applicable in an analogousmanner to the other methods described herein. For example, methods 2200,2300, 2500, 3200, 3400, and 3500 may include one or more of thecharacteristics of the various processes described above with referenceto method 2400. For brevity, these details are not repeated in thedescriptions of the other processes. The various methods and techniquesdescribed above with reference to method 2400 may be optionallyimplemented as one or more hardware units, such as those described withregard to FIGS. 5B and 29.

FIG. 25 is a flow diagram illustrating a method for displaying andmanaging notifications using an electronic device in accordance withsome embodiments. Method 2500 may be performed at an electronic devicewith a touch-sensitive display screen, such as device 100, 300 and/or500 (FIGS. 1, 3, 5, and 30). Some operations in method 2500 may becombined, the order of some operations may be changed, and someoperations may be omitted.

As described below, method 2500 provides an intuitive way for invokingdisplay of alert notifications. The method reduces the cognitive burdenon a user by reducing the number of inputs required to displayinformation of interest to a user. For battery-operated computingdevices, enabling a user to display and manage alert notificationsfaster and more efficiently conserves power and increase the timebetween battery charges.

At block 2502, the device obtains a plurality of alerts corresponding toat least two installed applications. At block 2504, the device displaysa first set of user interface objects (e.g., 604). At block 2506, thedevice detects a rotation of a rotatable input device (e.g., 506). Atblock 2508, in response to detecting the rotation, the device determineswhether the first set of user interface objects meets a thresholdcriteria. At block 2510, in accordance with a determination that thefirst set of user interface objects meets the threshold criteria, thedevice replaces display of the first set of user interface objects withdisplay of a plurality of notifications representing the plurality ofalerts (as depicted in, for example, FIG. 18). At block 2512, inaccordance with a determination that the first set of user interfaceobjects does not meet the threshold criteria, the device display asecond set of user interface objects (e.g., 1804), wherein the secondset is larger than the first set and comprises the first set.

Note that details of the processes described above with respect tomethod 2500 (e.g., FIGS. 25 and 18) are also applicable in an analogousmanner to the other methods described herein. For example, methods 2200,2300, 2400, 3200, 3400, and 3500 may include one or more of thecharacteristics of the various processes described above with referenceto method 2500. For brevity, these details are not repeated in thedescriptions of the other processes. The various methods and techniquesdescribed above with reference to method 2500 may be optionallyimplemented as one or more hardware units, such as those described withregard to FIGS. 5B and 30.

FIG. 32 is a flow diagram illustrating a method for displaying andmanaging notifications using an electronic device in accordance withsome embodiments. Method 3200 may be performed at an electronic devicewith a touch-sensitive display screen, such as device 100, 300 and/or500 (FIGS. 1, 3, 5, and 33). Some operations in method 3200 may becombined, the order of some operations may be changed, and someoperations may be omitted.

As described below, method 3200 provides an intuitive way for invokingdisplay of alert notifications. The method reduces the cognitive burdenon a user by reducing the number of inputs required to displayinformation of interest to a user. For battery-operated computingdevices, enabling a user to display and manage alert notificationsfaster and more efficiently conserves power and increase the timebetween battery charges.

At block 3202, the device receives a plurality of alerts. In someembodiments, the alerts are associated with date-times, include content,and/or correspond to a plurality of installed applications. At block3204, the device detects a user input (e.g., as depicted in FIGS. 6,11B, 12, 13, 14, 17, and 18). At block 3206, the device displays anotification interface on the display in response to detecting the userinput (e.g., 1920). In some embodiments, the notification interfacecomprises a plurality of notifications (e.g., 1926-1938) representing atleast a subset of the plurality of alerts. In some embodiments, thenotifications are displayed in a chronological order based on thedate-times associated with the alerts. In some embodiments, thenotifications include user interface objects representative of thecorresponding installed applications of the alerts (e.g., 1943-1945). Insome embodiments, the notifications include at least a portion of thecontent of the plurality of alerts (e.g., 1941, 1942).

Note that details of the processes described above with respect tomethod 3200 (e.g., FIGS. 32 and 19A-19C) are also applicable in ananalogous manner to the other methods described herein. For example,methods 2200, 2300, 2400, 2500, 3400, and 3500 may include one or moreof the characteristics of the various processes described above withreference to method 3200. For brevity, these details are not repeated inthe descriptions of the other processes. The various methods andtechniques described above with reference to method 3200 may beoptionally implemented as one or more hardware units, such as thosedescribed with regard to FIGS. 5B and 33.

In accordance with some embodiments, FIG. 26 shows an exemplaryfunctional block diagram of an electronic device 2600 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2600 are configured to perform the techniques described above.The functional blocks of the device 2600 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 26 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 26, an electronic device 2600 includes atouch-sensitive display unit 2602 configured to display a graphic userinterface and receive contacts, optionally, a rotatable input mechanismunit 2604, and a processing unit 2608 coupled to the touch-sensitivedisplay unit 2602 and, optionally, the rotatable input mechanism unit2604. In some embodiments, the touch-sensitive display unit 2602includes one or more sensor units 2606 configured to detect theintensity of contacts with the touch-sensitive display unit 2602. Insome embodiments, the processing unit 2608 includes an obtaining unit2610, a detecting unit 2612, a display enabling unit 2614, a scrollingunit 2616, a determining unit 2618, a scroll ceasing unit 2620, are-display enabling unit 2622, a zooming unit 2624, a display ceasingunit 2626, and a refreshing unit 2628.

The processing unit 2608 is configured to: obtain (e.g., with obtainingunit 2610) a plurality of alerts associated with date-times; detect(e.g., with detecting unit 2612) a user input; in response to detectingthe user input: obtain (e.g., with obtaining unit 2610) a currentdate-time, and enable display (e.g., with display enabling unit 2614) ofa notification interface on the touch-sensitive display unit 2602, thenotification interface comprising: a first notification representing afirst alert of the plurality of alerts associated with a date-time afterthe current date-time, a second notification representing a second alertof the plurality of alerts associated with a date-time before thecurrent date-time, and a graphical separator between the firstnotification and the second notification, wherein the graphicalseparator comprises an indication of the current date-time, wherein thefirst alert and the second alert correspond to different installedapplications.

In some embodiments, the first notification represents the nextimmediate upcoming alert in the plurality of alerts, based on thecurrent date-time.

In some embodiments, processing unit 2608 is further configured to:detect (e.g., with detecting unit 2612) a second user input; in responseto detecting the second user input, scroll (e.g., with scrolling unit2616) the notification interface in a first direction in accordance withthe second user input to display of additional notificationsrepresenting additional alerts in the plurality of alerts; determine(e.g., with determining unit 2618) whether the graphical separator hasbeen scrolled to a boundary of the touch-sensitive display unit 2602;and in accordance with a determination that the graphical separator hasbeen scrolled to the boundary of the touch-sensitive display unit 2602,cease to scroll (e.g., with scroll ceasing unit 2620) the graphicalseparator while continuing to scroll the additional notifications in thefirst direction in accordance with the second user input.

In some embodiments, the notification interface is displayed in aninitial position before scrolling and processing unit 2608 is furtherconfigured to: after scrolling the notification interface, detect (e.g.,with detecting unit 2612) a user selection of the graphical separator;and in response to detecting the selection, enable re-display (e.g.,with re-display enabling unit 2622) of the notification interface in theinitial position.

In some embodiments, electronic device 2600 further includes a rotatableinput mechanism unit 2604, wherein processing unit 2608 is coupled torotatable input mechanism unit 2604, and the second user input is arotation of rotatable input mechanism unit 1604.

In some embodiments, the second user input is a substantially verticalswipe or flick on touch-sensitive display unit 2602.

In some embodiments, electronic device 2600 further includes a rotatableinput mechanism unit 2604, wherein processing unit 2608 is coupled torotatable input mechanism unit 2604, and processing unit 2608 is furtherconfigured to: while displaying the notification interface, detect(e.g., with detecting unit 2612) a touch on touch-sensitive display unit2602 and detect (e.g., with detecting unit 2612) a rotation of rotatableinput mechanism unit 2604; and in response to detecting the touch andthe rotation, zoom (e.g., with zooming unit 2624) the notificationinterface.

In some embodiments, the touch and at least a portion of the rotationare detected essentially simultaneously.

In some embodiments, the first alert comprises content, and processingunit 2608 is further configured to: detect (e.g., with detecting unit2612) a contact on the first notification; and in response to detectingthe contact: cease to display (e.g., with display ceasing unit 2626) thenotification interface, and enable display (e.g., with display enablingunit 2614) of the content.

In some embodiments, processing unit 2608 is further configured to:after displaying the information, detect (e.g., with detecting unit2612) a third user input; and in response to detecting the third userinput: refresh (e.g., with refreshing unit 2628) the current date-time,and enable re-display (e.g., with re-display enabling unit 2622) of thenotification interface based on the refreshed current date-time, whereinthe notification interface excludes the first notification.

In some embodiments, the first notification comprises a first affordancefor launching a first installed application corresponding to the firstalert, and wherein the second notification comprises a second affordancefor launching a second installed application corresponding to the secondalert.

In some embodiments, launching the first or second installed applicationcomprises displaying the first or second installed application ontouch-sensitive display unit 2602.

In some embodiments, touch-sensitive display unit 2602 comprises one ormore sensor units 2606 to detect the intensity of contacts withtouch-sensitive display unit 2602, the notification interface comprisesa plurality of notifications representing at least a subset of theplurality of alerts, and processing unit 2608 is further configured to:while displaying the notification interface, detect (e.g., withdetecting unit 2612) a contact on the touch-sensitive display unit 2602;determine (e.g., with determining unit 2618) whether the characteristicintensity of the contact is above a threshold intensity; in accordancewith a determination that the characteristic intensity of the contact isabove the threshold intensity, enable display (e.g., with displayenabling unit 2614) of an affordance for removing the plurality ofnotifications from the notification interface; and in accordance with adetermination that the characteristic intensity of the contact is belowthe threshold intensity, and in accordance with a determination that thecontact is at a location on touch-sensitive display unit 2602corresponding to a third notification of the plurality of notifications,wherein the third notification represents a third alert of the pluralityof alerts, and wherein the third alert comprises content: cease todisplay (e.g., with display ceasing unit 2626) the notificationinterface, and enable display (e.g., with display enabling unit 2614) ofthe content.

In some embodiments, the notification interface comprises a plurality ofnotifications representing at least a subset of the plurality of alerts,and wherein displaying the notification interface comprises displayingthe plurality of notifications in a chronological order based on thedate-times associated with the at least a subset of the plurality ofalerts.

In some embodiments, displaying the notification interface comprisesdisplaying the plurality of notifications in an order based on theapplications corresponding to the at least a subset of the plurality ofalerts.

In some embodiments, displaying the notification interface comprisesdisplaying the plurality of notifications in an order based on aplurality of sources associated with the at least a subset of theplurality of alerts.

In some embodiments, the plurality of alerts comprises a location-basedalert, and wherein displaying the notification interface comprisesdisplaying a notification representing the location-based alert at thetop of the notification interface regardless of the value of anydate-time associated with the location-based alert.

The operations described above with reference to FIG. 22 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.26. For example, obtaining operation 2202, detecting operation 2204, anddisplaying operation 2206 may be implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a user input event, such as a contact on touch-sensitivedisplay 112, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether the user input corresponds to apredefined event or sub event, such as a request to launch anapplication or activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 27 shows an exemplaryfunctional block diagram of an electronic device 2700 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2700 are configured to perform the techniques described above.The functional blocks of the device 2700 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 27 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 27, an electronic device 2700 includes atouch-sensitive display unit 2702 configured to display a graphic userinterface and receive contacts, optionally, a rotatable input mechanismunit 2704, and a processing unit 2708 coupled to the touch-sensitivedisplay unit 2702 and, optionally, the rotatable input mechanism unit2704. In some embodiments, the touch-sensitive display unit 2702includes one or more sensor units 2706 configured to detect theintensity of contacts with the touch-sensitive display unit 2702. Insome embodiments, the processing unit 2708 includes an obtaining unit2710, a detecting unit 2712, a display enabling unit 2714, a determiningunit 2716, a launching unit 2718, a zooming unit 2720, a display ceasingunit 2722, a refreshing unit 2724, and a re-display enabling unit 2726.

The processing unit 2708 is configured to: obtain (e.g., with obtainingunit 2710) a plurality of alerts associated with date-times; detect(e.g., with detecting unit 2712) a first user input; in response todetecting the first user input: obtain (e.g., with obtaining unit 2710 afirst current date-time, and enable display (e.g., with display enablingunit 2714) of a plurality of past notifications representing a pluralityof past alerts from the plurality of alerts, wherein the plurality ofpast alerts are associated with date-times before the current date-time,and wherein the plurality of past alerts correspond to a first pluralityof installed applications; detect (e.g., with detecting unit 2712) acontact on the touch-sensitive display unit 2702; determine (e.g., withdetermining unit 2716) whether the contact is a tap or a substantiallyhorizontal swipe; in response to a determination that the contact is asubstantially horizontal swipe: obtain (e.g., with obtaining unit 2710)a second current date-time, and enable display (e.g., with displayenabling unit 2714) of a plurality of future notifications representinga plurality of future alerts from the plurality of alerts, wherein theplurality of future alerts are associated with date-times after thesecond current date-time, and wherein the plurality of future alertscorrespond to a second plurality of installed applications.

In some embodiments, processing unit 2708 is further configured to: inaccordance with a determination that the contact is a tap, and whereinthe tap is detected at a location on the touch-sensitive display unit2702 corresponding to a past notification of the plurality of pastnotifications, launch (e.g., with launching unit 2718) the installedapplication corresponding to the past alert represented by the pastnotification.

In some embodiments, electronic device 2700 further includes a rotatableinput mechanism unit 2704, wherein processing unit 2708 is coupled tothe rotatable input mechanism unit 2704 and processing unit 2708 isfurther configured to: while displaying the plurality of pastnotifications or the plurality of future notifications, detect (e.g.,with detecting unit 2712) a second contact on the touch-sensitivedisplay unit 2702 and detect (e.g., with detecting unit 2712) a rotationof the rotatable input mechanism unit 2704; in response to detecting thesecond contact and the rotation, zoom (e.g., with zooming unit 2720) thedisplayed plurality of past notifications or plurality futurenotifications.

In some embodiments, the second contact and at least a portion of therotation occur essentially simultaneously.

In some embodiments, processing unit 2708 is further configured to:while displaying the plurality of past notifications, detect (e.g., withdetecting unit 2712) a third contact on the touch-sensitive display unit2702 at a location corresponding to a first past notification, whereinthe first past notification represents an alert in the plurality ofalerts and wherein the alert comprises content; and in response todetecting the third contact: cease to display (e.g., with displayceasing unit 2722) the plurality of past notifications, and enabledisplay (e.g., with display enabling unit 2714) of the content.

In some embodiments, processing unit 2708 is further configured to:after displaying the content, detect (e.g., with detecting unit 2712) athird user input; and in response to detecting the third user input:refresh (e.g., with refreshing unit 2724) the current date-time, andenable re-display (e.g., with re-display enabling unit 2726) of theplurality of past notifications based on the refreshed currentdate-time, wherein the plurality of past notifications excludes thefirst past notification.

In some embodiments, the touch-sensitive display comprises one or moresensor units 2706 to detect the intensity of contacts with thetouch-sensitive display unit 2702 and processing unit 2708 is furtherconfigured to: while displaying a plurality of past or futurenotifications, detect (e.g., with detecting unit 2712) a fourth contacton the touch-sensitive display unit 2702; determine (e.g., withdetermining unit 2716) whether the characteristic intensity of thefourth contact is above a threshold intensity; in accordance with adetermination that the characteristic intensity of the fourth contact isabove the threshold intensity, enable display (e.g., with displayenabling unit 2714) of an affordance for removing the displayedplurality of past or future notifications; and in accordance with adetermination that the intensity of the fourth contact is below thethreshold intensity, and in response to detecting the fourth contact ata location on touch-sensitive display unit 2702 corresponding to a firstnotification of the plurality of past or future notifications, the firstnotification representing a first alert of the plurality of alerts,wherein the first alert comprises content: cease to display (e.g., withdisplay ceasing unit 2722) the plurality of past or futurenotifications, and enable display (e.g., with display enabling unit2714) of the content.

In some embodiments, the plurality of past notifications are displayedin a first chronological order based on the date-times associated withthe plurality of past alerts, and wherein the plurality of futurenotifications are displayed in a second chronological order based on thedate-times associated with the plurality of future alerts.

In some embodiments, the plurality of past notifications are displayedin a third order based on the applications corresponding to theplurality of past alerts, and wherein the plurality of futurenotifications are displayed in a fourth order based on the applicationscorresponding to the plurality of past alerts.

In some embodiments, the third order and the fourth order are the sameorder.

In some embodiments, the plurality of past notifications are displayedin a fifth order based on a plurality of sources associated with theplurality of past alerts, and wherein the plurality of pastnotifications are displayed in a sixth order based on a plurality ofsources associated with the plurality of future alerts.

In some embodiments, the fifth order and the sixth order are the sameorder.

The operations described above with reference to FIG. 23 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.27. For example, obtaining operation 2302, detecting operations 2304 and2308, displaying operations 2306 and 231, and determining operation 2310may be implemented by event sorter 170, event recognizer 180, and eventhandler 190. Event monitor 171 in event sorter 170 detects a user inputevent, such as a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether the user input corresponds to a predefined event orsub event, such as a request to launch an application or activation ofan affordance on a user interface. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 may utilize or call data updater 176 or object updater 177to update the application internal state 192. In some embodiments, eventhandler 190 accesses a respective GUI updater 178 to update what isdisplayed by the application. Similarly, it would be clear to a personhaving ordinary skill in the art how other processes can be implementedbased on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 28 shows an exemplaryfunctional block diagram of an electronic device 2800 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2800 are configured to perform the techniques described above.The functional blocks of the device 2800 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 28 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 28, an electronic device 2800 includes atouch-sensitive display unit 2802 configured to display a graphic userinterface and receive contacts and a processing unit 2804 coupled to thetouch-sensitive display unit 2802. In some embodiments, processing unit2804 includes an obtaining unit 2806, a detecting unit 2808, a displayenabling unit 2810, a determining unit 2812, and a launching unit 2814.

The processing unit 2804 is configured to: obtain (e.g., with obtainingunit 2806) a plurality of alerts associated with date-times; detect(e.g., with detecting unit 2808) a first user input; in response todetecting the first user input: obtain (e.g., with obtaining unit 2806)a first current date-time; enable display (e.g., with display enablingunit 2810) of a plurality of future notifications representing aplurality of future alerts from the plurality of alerts, wherein theplurality of future alerts are associated with date-times after thefirst current date-time, and wherein the plurality of future alertscorrespond to a first plurality of installed applications; detect (e.g.,with detecting unit 2808) a contact on the touch-sensitive display unit2802; determine (e.g., with determining unit 2812) whether the contactis a tap or a substantially horizontal swipe; in accordance with adetermination that the contact is a substantially horizontal swipe:obtain (e.g., with obtaining unit 2806) a second current date-time; andenable display (e.g., with display enabling unit 2810) of a plurality ofpast notifications representing a plurality of past alerts from theplurality of alerts, wherein the plurality of past alerts are associatedwith date-times before the second current date-time, and wherein theplurality of past alerts correspond to a second plurality of installedapplications.

In some embodiments, processing unit 2804 is further configured to: inaccordance with a determination that the contact is a tap, wherein thetap is detected at a location on touch-sensitive display unit 2802corresponding to a first future notification of the plurality of futurenotifications, launch (e.g., with launching unit 2814) the installedapplication corresponding to the future alert represented by the firstfuture notification.

The operations described below with reference to FIG. 34 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.28. For example, obtaining operations 3402 and 3406, detectingoperations 3404 and 3408, determining operation 3410, and displayingoperations 3406 and 3412 may be implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a user input event, such as a contact on touch-sensitivedisplay 112, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether the user input corresponds to apredefined event or sub event, such as a request to launch anapplication or activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 29 shows an exemplaryfunctional block diagram of an electronic device 2900 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2900 are configured to perform the techniques described above.The functional blocks of the device 2900 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 29 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 29, an electronic device 2900 includes atouch-sensitive display unit 2902 configured to display a graphic userinterface and receive contacts and a processing unit 2904 coupled to thetouch-sensitive display unit 2902. In some embodiments, processing unit2904 includes an obtaining unit 2906, a detecting unit 2908, a displayenabling unit 2910, a determining unit 2912, a launching unit 2914, anda display replacing unit 2916.

The processing unit 2904 is configured to: obtain (e.g., with obtainingunit 2906) a plurality of alerts associated with date-times; detect(e.g., with detecting unit 2908) a first user input; in response todetecting the first user input: obtain (e.g., with obtaining unit 2906)a first current date-time, and enable display (e.g., with displayenabling unit 2910) of a plurality of past notifications representing aplurality of past alerts from the plurality of alerts, wherein theplurality of past alerts are associated with date-times before the firstcurrent date-time, and wherein the plurality of past alerts correspondto a first plurality of installed applications; detect (e.g., withdetecting unit 2908) a contact on the touch-sensitive display unit 2902;determine (e.g., with determining unit 2912) whether the contact is atap or a substantially horizontal swipe; in accordance with adetermination that the contact is a substantially horizontal swipe:obtain (e.g., with obtaining unit 2906) a second current date-time, andenable display (e.g., with display enabling unit 2910) of a singlefuture notification representing the most immediate upcoming alert inthe plurality of alerts relative to the second current date-time.

In some embodiments, processing unit 2904 is further configured to: inaccordance with a determination that the contact is a tap, wherein thetap is detected at a location on touch-sensitive display unit 2902corresponding to a first past notification of the plurality of pastnotifications, launch (e.g., with launching unit 2914) the installedapplication corresponding to the past alert represented by the firstpast notification.

In some embodiments, processing unit 2904 is further configured to:while the single future notification is displayed, detect (e.g., withdetecting unit 2908) a second contact on the touch-sensitive displayunit 2902; in response to detecting the second contact, determine (e.g.,with determining unit 2912) whether the second contact is a tap or asubstantially horizontal swipe; in accordance with a determination thatthe second contact is a substantially horizontal swipe, replace display(e.g., with display replacing unit 2916) of the single futurenotification with display of one or more indications of the user'sactivities; and in accordance with a determination that the secondcontact is a tap, and wherein the tap is detected at a locationcorresponding to the single future notification, launch (e.g., withlaunching unit 2914) the installed application corresponding to the mostimmediate upcoming alert represented by the single future notification.

The operations described above with reference to FIG. 24 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.29. For example, obtaining operation 2402, detecting operations 2404 and2408, displaying operation 2406 and determining operation 2410 may beimplemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a user input event,such as a contact on touch-sensitive display 112, and event dispatchermodule 174 delivers the event information to application 136-1. Arespective event recognizer 180 of application 136-1 compares the eventinformation to respective event definitions 186, and determines whetherthe user input corresponds to a predefined event or sub event, such as arequest to launch an application or activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 mayutilize or call data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 30 shows an exemplaryfunctional block diagram of an electronic device 3000 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 3000 are configured to perform the techniques described above.The functional blocks of the device 3000 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 30 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 30, an electronic device 3000 includes atouch-sensitive display unit 3002 configured to display a graphic userinterface and receive contacts, a rotatable input mechanism unit 3004,and a processing unit 3006 coupled to the touch-sensitive display unit3002 and the rotatable input mechanism unit 3004. In some embodiments,the processing unit 3006 includes an obtaining unit 3008, a displayenabling unit 3010, a detecting unit 3012, a determining unit 3014, anda display replacing unit 3016.

The processing unit 3006 is configured to: obtain (e.g., with obtainingunit 3008) a plurality of alerts; enable display (e.g., with displayenabling unit 3010) of a first set of user interface objects; detect(e.g., with detecting unit 3012) a rotation of the rotatable inputmechanism unit 3004; in response to detecting the rotation: determine(e.g., with determining unit 3014) whether the first set of userinterface objects meets a threshold criteria; in accordance with adetermination that the first set of user interface objects meets thethreshold criteria, replace display (e.g., with display replacing unit3016) of the first set of user interface objects with display of aplurality of notifications representing at least a subset of theplurality of alerts; and in accordance with a determination that thefirst set of user interface objects does not meet the thresholdcriteria, enable display (e.g., with display enabling unit 3010) of asecond set of user interface objects, wherein the second set is largerthan the first set and comprises the first set.

In some embodiments, replacing display of the first set of userinterface objects with display of a plurality of notificationscomprises: obtaining a current date-time; and displaying a notificationinterface on touch-sensitive display unit 3002, the notificationinterface comprising: a first notification representing a first alert ofthe plurality of alerts, wherein the first alert is associated with adate-time before the current date-time, a second notificationrepresenting a second alert of the plurality of alerts, wherein thesecond alert is associated with a date-time after the current date-time,and a graphical separator between the first notification and the secondnotification, wherein the graphical separator comprises an indication ofthe current date-time, and wherein the first alert and the second alertcorrespond to different installed applications.

In some embodiments, the plurality of alerts are associated with aplurality of date-times, and replacing display of the first set of userinterface objects with display of a plurality of notificationscomprises: obtaining a current date-time; displaying a plurality of pastnotifications representing a plurality of past alerts in the pluralityof alerts, wherein the plurality of past alerts are associated withdate-times before the current date-time, wherein the plurality of pastalerts correspond to a first plurality of installed applications;detecting a contact on the touch-sensitive display unit 3002;determining whether the contact is a swipe or a tap; in accordance witha determination that the contact is a horizontal swipe, displaying aplurality of future notifications representing a plurality of futurealerts in the plurality of alerts, wherein the plurality of futurealerts are associated with date-times after the current date-time, andwherein the plurality of future alerts correspond to a second pluralityof installed applications.

In some embodiments, the plurality of alerts are associated with aplurality of date-times, and wherein replacing display of the first setof user interface objects with display of a plurality of notificationscomprises: displaying a plurality of past notifications representing aplurality of past alerts from the plurality of alerts, wherein theplurality of past alerts are associated with date-times before the firstcurrent date-time, and wherein the plurality of past alerts correspondto a first plurality of installed applications; detecting a contact onthe touch-sensitive display unit 3002; determining whether the contactis a tap or a substantially horizontal swipe; in accordance with adetermination that the contact is a substantially horizontal swipe:obtaining a second current date-time, and displaying a single futurenotification representing the most immediate upcoming alert in theplurality of alerts relative to the second current date-time.

In some embodiments, in accordance with a determination that the contactis a tap, wherein the tap is detected at a location on touch-sensitivedisplay unit 3002 corresponding to a first past notification of theplurality of past notifications, launching the installed applicationcorresponding to the past alert represented by the first pastnotification.

The operations described above with reference to FIG. 25 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.30. For example, obtaining operation 2502, displaying operation 2504,and detecting operation 2506 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a user input event, such as a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether the user inputcorresponds to a predefined event or sub event, such as a request tolaunch an application or activation of an affordance on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 may utilize orcall data updater 176 or object updater 177 to update the applicationinternal state 192. In some embodiments, event handler 190 accesses arespective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 31 shows an exemplaryfunctional block diagram of an electronic device 3100 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 3100 are configured to perform the techniques described above.The functional blocks of the device 3100 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 31 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 31, an electronic device 3100 includes atouch-sensitive display unit 3102 configured to display a graphic userinterface and receive contacts, a communication unit 3104 configured tocommunicate wirelessly with an external device and coupled to thetouch-sensitive display unit 3102, and a processing unit 3106 coupled tothe touch-sensitive display unit 3102 and the communication unit 3104.In some embodiments, the processing unit 3106 includes a receiving unit3108, a display enabling unit 3110, and a send enabling unit 3112.

The processing unit 3106 is configured to: receive (e.g., with receivingunit 3108) application data associated with an installed application;enable display (e.g., with display enabling unit 3110), on thetouch-sensitive display unit 3102, a first indication indicating receiptof the application data; receive (e.g., with receiving unit 3108) auser's indication indicating whether the electronic device 3100 is toinstruct an external device to display an indication indicating receipt,by the electronic device 3100, of application data associated with theinstalled application; and in response to the user's indication toinstruct the external device: enable sending (e.g., with send enablingunit 3112) data to the external device (e.g., with communication unit3104), wherein the data causes the external device to display a secondindication indicating receipt of the application data.

The operations described below with reference to FIG. 35 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.31. For example, receiving operations 3502 and 3506, displayingoperation 3504, and sending operation 3508 may be implemented by eventsorter 170, event recognizer 180, event handler 190, and peripheralsinterface 118. Peripherals interface 118 receives data. Event monitor171 in event sorter 170 detects a user input event, such as a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether the user inputcorresponds to a predefined event or sub event, such as a user'sindication of whether an external device is to be instructed to displayan indication of receipt of application data. When a respectivepredefined event or sub-event is detected, event recognizer 180activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. In some embodiments,event handler 190 causes data to be sent to an external device usingperipherals interface 118. Similarly, it would be clear to a personhaving ordinary skill in the art how other processes can be implementedbased on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 33 shows an exemplaryfunctional block diagram of an electronic device 3300 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 3300 are configured to perform the techniques described above.The functional blocks of the device 3300 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 33 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 33, an electronic device 3300 includes atouch-sensitive display unit 3302 configured to display a graphic userinterface and receive contacts. Optionally, the touch-sensitive displayunit 3302 includes a sensor unit 3306. Electronic device 3300 furtherincludes a rotatable input mechanism unit 3304 and a processing unit3308 coupled to the touch-sensitive display unit 3302 and the rotatableinput mechanism unit 3304. In some embodiments, processing unit 3308includes a receiving unit 3310, a detecting unit 3312, a displayenabling unit 3314, a launching unit 3316, and a determining unit 3318.

Processing unit 3308 is configured to receive (e.g., with receiving unit3310) a plurality of alerts, where the alerts are associated withdate-times, include content, and correspond to a plurality of installedapplications. Processing unit 3308 is further configured to detect(e.g., with detecting unit 3312) a user input and, in response todetecting the user input, enable (e.g., with display enabling unit 3314)display of a notification interface on the display unit. Thenotification interface comprises a plurality of notificationsrepresenting at least a subset of the plurality of alerts, where thenotifications are displayed in a chronological order based on thedate-times associated with the alerts. The notifications include userinterface objects representative of the corresponding installedapplications of the alerts and include at least a portion of the contentof the plurality of alerts.

In some embodiments, processing unit 3308 is further configured todetect (e.g., with detecting unit 3312) a second user input whiledisplaying the notification interface, and, in response to detecting thesecond user input, enable (e.g., with display enabling unit 3314)scrolling of the notification interface in a first direction inaccordance with the second user input to display additionalnotifications representing additional alerts in the plurality of alerts.In some embodiments, the second user input is a rotation of therotatable input mechanism unit 3304. In some embodiments, the seconduser input is a substantially vertical swipe, drag, or flick on thetouch-sensitive display unit.

In some embodiments, processing unit 3308 is further configured to,further in response to detecting the second user input, enable (e.g.,with display enabling unit 3314) display of an indication based on thecurrently displayed notifications relative to an entire set ofnotifications associated with the plurality of received alerts. In someembodiments, the indication is representative of a position of thecurrently displayed notifications relative to the entire set ofnotifications. In some embodiments, the indication is representative ofa proportion of the entire set of notifications that are currentlydisplayed. In some embodiments, the indication is displayed in a fixedlocation. In some embodiments, rotatable input mechanism unit 3304 isadjacent to the touch-sensitive display unit 3302, and the fixedlocation is adjacent to the rotatable input mechanism unit 3304. In someembodiments, the indication is displayed over at least a portion of oneor more notifications. In some embodiments, processing unit 3308 isfurther configured to enable (e.g., with display enabling unit 3314)ceasing display of the indication in accordance with a predeterminedamount of time of inactivity after the second input. In someembodiments, the indication is ceased to be displayed by fading out theindication over time.

In some embodiments, processing unit 3308 is further configured to,while displaying the notification interface, detect (e.g., withdetecting unit 3312) a touch on the touch-sensitive display unit, detect(e.g., with detecting unit 3312) a rotation of the rotatable inputmechanism unit 3304, and enable (e.g., with display enabling unit 3314)zooming of the notification interface in response to detecting the touchand the rotation. In some embodiments, the touch and at least a portionof the rotation are detected essentially simultaneously.

In some embodiments, the plurality of notifications includes a firstnotification corresponding to a first alert and the first alertcomprises first content. Processing unit 3308 is further configured todetect (e.g., with detecting unit 3312) a contact on the firstnotification and, in response to detecting the contact, enable (e.g.,with display enabling unit 3314) ceasing display of the notificationinterface, and enable (e.g., with display enabling unit 3314) display ofthe first content. In some embodiments, the contact is detected on theuser interface object representative of the corresponding installedapplication of the first alert. In some embodiments, processing unit3308 is further configured to detect (e.g., with detecting unit 3312) athird user input after displaying the first content, and in response todetecting the third user input, enable (e.g., with display enabling unit3314) re-display of the notification interface, where the notificationinterface excludes the first notification.

In some embodiments, the plurality of notifications includes a firstnotification and a second notification, where the first notificationincludes a first user interface object representative of a firstinstalled application corresponding to a first alert and the secondnotification includes a second user interface object representative of asecond installed application corresponding to a second alert. In someembodiments, the first user interface object includes a first affordancethat, when activated, enables launching (e.g., with launching unit 3316)of the first installed application corresponding to the first alert, andthe second user interface object includes a second affordance that, whenactivated, enables launching (e.g., with launching unit 3316) of thesecond installed application corresponding to the second alert. In someembodiments, launching the first installed application or the secondinstalled application comprises displaying the first installedapplication or the second installed application on the touch-sensitivedisplay unit.

In some embodiments, sensor unit 3306 is configured to detect theintensity of contacts with the touch-sensitive display unit, andprocessing unit 3308 is further configured to detect (e.g., withdetecting unit 3312) a contact on the display while displaying thenotification interface. Processing unit 3308 is further configured todetermine (e.g., with determining unit 3318) whether the characteristicintensity of the contact is above a threshold intensity and, inaccordance with a determination that the characteristic intensity of thecontact is above the threshold intensity, enable (e.g., with displayenabling unit 3314) display of an affordance for removing the pluralityof notifications from the notification interface.

In some embodiments, processing unit 3308 is further configured to: inaccordance with a determination that the characteristic intensity of thecontact is below the threshold intensity, and in accordance with adetermination that the contact is at a location on the displaycorresponding to a third notification of the plurality of notifications,where the third notification represents a third alert of the pluralityof alerts, and where the third alert comprises third content: enable(e.g., with display enabling unit 3314) ceasing display of thenotification interface, and enable (e.g., with display enabling unit3314) display of the third content.

In some embodiments, the plurality of alerts comprises a location-basedalert, and displaying the notification interface comprises displaying anotification representing the location-based alert at the top of thenotification interface regardless of the value of any date-timeassociated with the location-based alert. In some embodiments,displaying the notification interface includes replacing display of afirst set of user interface objects with display of the notificationinterface.

The operations described above with reference to FIG. 32 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.33. For example, receiving operation 3202, detecting operation 3204, anddisplaying operation 3206 may be implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a user input event, such as a contact on touch-sensitivedisplay 112, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether the user input corresponds to apredefined event or sub event, such as a request to launch anapplication or activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

FIG. 34 is a flow diagram illustrating a method for displaying andmanaging notifications using an electronic device in accordance withsome embodiments. Method 3400 may be performed at an electronic devicewith a touch-sensitive display screen, such as device 100, 300 and/or500 (FIGS. 1, 3, 5, and 28). Some operations in method 3400 may becombined, the order of some operations may be changed, and someoperations may be omitted.

As described below, method 3400 provides an intuitive way for invokingdisplay of alert notifications. The method reduces the cognitive burdenon a user by reducing the number of inputs required to displayinformation of interest to a user. For battery-operated computingdevices, enabling a user to display and manage alert notificationsfaster and more efficiently conserves power and increase the timebetween battery charges.

At block 3402, the device obtains a plurality of alerts associated withdate-times. At block 3404, the device detects a user input. In someembodiments, the user input may be a touch, tap, or swipe on thetouchscreen (e.g., 112, 355, 504). In some embodiments, the user inputmay be a rotation of a rotatable input mechanism (e.g., 506). At block3406, in response to detecting the user input, the device obtains acurrent date-time, and displays a plurality of future notifications(e.g., 1308) representing a plurality of past alerts associated withdate-times after the current date-time (as depicted in FIG. 13, forexample). The plurality of future alerts correspond to a first pluralityof installed applications. At block 3408, the device detects a contacton the touchscreen (e.g., 112, 355, 504). At block 3410, the devicedetermines whether the contact was a tap or a substantially horizontalswipe. At block 3412, in accordance with a determination that thecontact was a substantially horizontal swipe, the device displays aplurality of past notifications (e.g., 1310) representing a plurality ofpast alerts associated with date-times before the current date-time (asdepicted in FIG. 13, for example). The plurality of past alertscorresponds to a second plurality of installed applications.

Note that details of the processes described above with respect tomethod 3400 (e.g., FIGS. 34 and 12) are also applicable in an analogousmanner to the other methods described herein. For example, methods 2200,2300, 2400, 2500, 3200, and 3500 may include one or more of thecharacteristics of the various processes described above with referenceto method 3400. For brevity, these details are not repeated in thedescriptions of the other processes. The various methods and techniquesdescribed above with reference to method 3400 may be optionallyimplemented as one or more hardware units, such as those described withregard to FIGS. 5B and 28.

FIG. 35 is a flow diagram illustrating a method for displaying andmanaging notifications using an electronic device in accordance withsome embodiments. Method 3500 may be performed at an electronic devicewith a touch-sensitive display screen, such as device 100, 300 and/or500 (FIGS. 1, 3, 5, and 31). Some operations in method 3500 may becombined, the order of some operations may be changed, and someoperations may be omitted.

As described below, method 3500 provides an intuitive way for invokingdisplay of alert notifications. The method reduces the cognitive burdenon a user by reducing the number of inputs required to displayinformation of interest to a user. For battery-operated computingdevices, enabling a user to display and manage alert notificationsfaster and more efficiently conserves power and increase the timebetween battery charges.

At block 3502, the device receives application data associated with theinstalled application. At block, 3504, the device displays a firstindication indicating receipt of the application data. At block 3506,the device receives a user's indication indicating whether the device isto instruct the external device to display an indication indicatingreceipt, by the device, of application data associated with theinstalled application. At block 3508, the device, in response to theuser's indication to instruct the external device, sends data to theexternal device, where the data causes the external device to display asecond indication indicating receipt of the application data.

Note that details of the processes described above with respect tomethod 3500 (e.g., FIG. 35) are also applicable in an analogous mannerto the other methods described herein. For example, methods 2200, 2300,2400, 2500, 3200, and 3400 may include one or more of thecharacteristics of the various processes described above with referenceto method 3500. For brevity, these details are not repeated in thedescriptions of the other processes. The various methods and techniquesdescribed above with reference to method 3500 may be optionallyimplemented as one or more hardware units, such as those described withregard to FIGS. 5B and 31.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

What is claimed is:
 1. A non-transitory computer-readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by one or more processors of awearable electronic device with a touch-sensitive display and arotatable input mechanism that is physically rotatable relative to ahousing of the electronic device and adjacent to the display, cause thedevice to: receive a plurality of alerts, wherein the alerts includecontent, and wherein the alerts correspond to a plurality of installedapplications; detect a user input; in response to detecting the userinput, display a notification interface on the display, the notificationinterface comprising a plurality of notifications representing at leasta subset of the plurality of alerts; while displaying the notificationinterface, detect a second user input that includes a first rotation ofthe rotatable input mechanism relative to the housing of the electronicdevice; and in response to detecting the second user input that includesthe first rotation of the rotatable input mechanism relative to thehousing of the electronic device: scroll the notification interface in afirst direction in accordance with the second user input, based on anamount of the first rotation of the rotatable input mechanism relativeto the housing of the electronic device, to concurrently displayadditional notifications representing additional alerts in the pluralityof alerts; and display an indication determined in accordance with aplurality of currently displayed notifications relative to an entire setof notifications associated with the plurality of received alerts,wherein the indication comprises a stationary user interface objectrepresentative of the entire set of notifications and a movable userinterface object representative of the plurality of currently displayednotifications, wherein the stationary user interface object is displayedin a fixed location while scrolling the notification interface in thefirst direction in accordance with the second input, wherein the movableuser interface object moves relative to the stationary user interfaceobject while scrolling the notification interface in the first directionin accordance with the second input, wherein a height of the stationaryuser interface object is not greater than a height of at least onenotification of the concurrently displayed additional notifications,wherein the stationary user interface object and the movable userinterface object were not displayed on the display prior to detectingthe second user input, and wherein the fixed location is adjacent to therotatable input mechanism that is physically rotatable relative to thehousing of the electronic device.
 2. The non-transitorycomputer-readable storage medium according to claim 1, wherein theindication is representative of a position of the currently displayednotifications relative to the entire set of notifications.
 3. Thenon-transitory computer-readable storage medium according to claim 1,wherein the indication is representative of a proportion of thecurrently displayed notifications compared to the entire set ofnotifications.
 4. The non-transitory computer-readable storage mediumaccording to claim 1, wherein the indication is displayed over at leasta portion of one or more of the notifications.
 5. The non-transitorycomputer-readable storage medium according to claim 1, furthercomprising instructions to cause the device to: in accordance with adetermination that rotational input is not detected, via the rotatableinput mechanism, for a predetermined amount of time of inactivity afterdetecting the second user input that includes the first rotation of therotatable input mechanism relative to the housing of the electronicdevice, cease to display the indication.
 6. The non-transitorycomputer-readable storage medium according to claim 5, wherein theindication is ceased to be displayed by fading out the indication overtime.
 7. The non-transitory computer-readable storage medium accordingto claim 1, further comprising instructions to cause the device to:while displaying the notification interface, detect a touch on thetouch-sensitive display and detect a second rotation of the rotatableinput mechanism; and in response to detecting the touch and the secondrotation, zoom the notification interface.
 8. The non-transitorycomputer-readable storage medium according to claim 7, wherein the touchand at least a portion of the second rotation are detectedsimultaneously.
 9. The non-transitory computer-readable storage mediumaccording to claim 1, wherein the plurality of notifications includes afirst notification corresponding to a first alert, and wherein the firstalert comprises first content, further comprising instructions to causethe device to: detect a first contact on the first notification; and inresponse to detecting the first contact on the first notification: ceaseto display the notification interface; and display the first content.10. The non-transitory computer-readable storage medium according toclaim 9, wherein the first contact on the first notification is detectedon a user interface object representative of a corresponding installedapplication of the first alert.
 11. The non-transitory computer-readablestorage medium according to claim 9, further comprising instructions tocause the device to: after displaying the first content, detect a thirduser input; and in response to detecting the third user input:re-display the notification interface, wherein the notificationinterface excludes the first notification.
 12. The non-transitorycomputer-readable storage medium according to claim 1, wherein theplurality of notifications includes a first notification and a secondnotification, wherein the first notification includes a first userinterface object representative of a first installed applicationcorresponding to a first alert and the second notification includes asecond user interface object representative of a second installedapplication corresponding to a second alert, wherein the first userinterface object includes a first affordance that, when activated,launches the first installed application corresponding to the firstalert, and wherein the second user interface object includes a secondaffordance that, when activated, launches the second installedapplication corresponding to the second alert.
 13. The non-transitorycomputer-readable storage medium according to claim 12, whereinlaunching the first installed application or the second installedapplication comprises displaying the first installed application or thesecond installed application on the touch-sensitive display.
 14. Thenon-transitory computer-readable storage medium according to claim 1,wherein the touch-sensitive display comprises one or more sensors todetect an intensity of contacts with the touch-sensitive display,further comprising instructions to cause the device to: while displayingthe notification interface, detect a second contact on the display;determine whether a characteristic intensity of the second contact isabove a threshold intensity; and in accordance with a determination thatthe characteristic intensity of the second contact is above thethreshold intensity, display an affordance for removing the plurality ofnotifications from the notification interface.
 15. The non-transitorycomputer-readable storage medium according to claim 14, furthercomprising instructions to cause the device to: in accordance with adetermination that the characteristic intensity of the second contact isbelow the threshold intensity and in accordance with a determinationthat the second contact is at a location on the display corresponding toa third notification of the plurality of notifications, wherein thethird notification represents a third alert of the plurality of alerts,and wherein the third alert comprises third content: cease to displaythe notification interface; and display the third content.
 16. Thenon-transitory computer-readable storage medium according to claim 1,wherein the plurality of alerts comprises a location-based alert, andwherein displaying the notification interface comprises displaying anotification representing the location-based alert at a top of thenotification interface regardless of a value of any date-time associatedwith the location-based alert.
 17. The non-transitory computer-readablestorage medium according to claim 1, wherein displaying the notificationinterface includes replacing display of a first set of user interfaceobjects with display of the notification interface.
 18. Thenon-transitory computer-readable storage medium according to claim 1,wherein the indication, which is in the fixed location on a side of thedisplay and adjacent to the rotatable input mechanism, is offset from acenter of the side of the touch-sensitive display.
 19. Thenon-transitory computer-readable storage medium according to claim 1,wherein: the concurrently displayed additional notifications comprise afirst notification and a second notification, and a height of thestationary user interface object is not greater than a height of thefirst notification and is not greater than a height of the secondnotification.
 20. The non-transitory computer-readable storage mediumaccording to claim 19, wherein the first notification and the secondnotification collectively have a collective height that is greater thanhalf a height of the touch-sensitive display.
 21. A method, comprising:at a wearable electronic device with a touch-sensitive display and arotatable input mechanism that is physically rotatable relative to ahousing of the electronic device and adjacent to the display: receivinga plurality of alerts, wherein the alerts include content, and whereinthe alerts correspond to a plurality of installed applications;detecting a user input; in response to detecting the user input,displaying a notification interface on the display, the notificationinterface comprising a plurality of notifications representing at leasta subset of the plurality of alerts; while displaying the notificationinterface, detecting a second user input that includes a first rotationof the rotatable input mechanism relative to the housing of theelectronic device; and in response to detecting the second user inputthat includes the first rotation of the rotatable input mechanismrelative to the housing of the electronic device: scrolling thenotification interface in a first direction in accordance with thesecond user input, based on an amount of the first rotation of therotatable input mechanism relative to the housing of the electronicdevice, to concurrently display additional notifications representingadditional alerts in the plurality of alerts; and displaying anindication determined in accordance with a plurality of currentlydisplayed notifications relative to an entire set of notificationsassociated with the plurality of received alerts, wherein the indicationcomprises a stationary user interface object representative of theentire set of notifications and a movable user interface objectrepresentative of the plurality of currently displayed notifications,wherein the stationary user interface object is displayed in a fixedlocation while scrolling the notification interface in the firstdirection in accordance with the second input, wherein a height of thestationary user interface object is not greater than a height of atleast one notification of the concurrently displayed additionalnotifications, wherein the stationary user interface object and themovable user interface object were not displayed on the display prior todetecting the second user input, and wherein the fixed location isadjacent to the rotatable input mechanism that is physically rotatablerelative to the housing of the electronic device.
 22. The method ofclaim 21, wherein the indication is representative of a position of thecurrently displayed notifications relative to the entire set ofnotifications.
 23. The method of claim 21, wherein the indication isrepresentative of a proportion of the currently displayed notificationscompared to the entire set of notifications.
 24. The method of claim 21,wherein the indication is displayed over at least a portion of one ormore of the notifications.
 25. The method of claim 21, furthercomprising: in accordance with a determination that rotational input isnot detected, via the rotatable input mechanism, for a predeterminedamount of time of inactivity after detecting the second user input thatincludes the first rotation of the rotatable input mechanism relative tothe housing of the electronic device, ceasing to display the indication.26. The method of claim 25, wherein the indication is ceased to bedisplayed by fading out the indication over time.
 27. The method ofclaim 21, further comprising: while displaying the notificationinterface, detecting a touch on the touch-sensitive display anddetecting a second rotation of the rotatable input mechanism; and inresponse to detecting the touch and the second rotation, zooming thenotification interface.
 28. The method of claim 27, wherein the touchand at least a portion of the second rotation are detectedsimultaneously.
 29. The method of claim 21, wherein the plurality ofnotifications includes a first notification corresponding to a firstalert, wherein the first alert comprises first content, and wherein themethod further comprises: detecting a first contact on the firstnotification; and in response to detecting the first contact on thefirst notification: ceasing to display the notification interface; anddisplaying the first content.
 30. The method of claim 29, wherein thefirst contact on the first notification is detected on a user interfaceobject representative of a corresponding installed application of thefirst alert.
 31. The method of claim 29, further comprising: afterdisplaying the first content, detect a third user input; and in responseto detecting the third user input: re-displaying the notificationinterface, wherein the notification interface excludes the firstnotification.
 32. The method of claim 21, wherein the plurality ofnotifications includes a first notification and a second notification,wherein the first notification includes a first user interface objectrepresentative of a first installed application corresponding to a firstalert and the second notification includes a second user interfaceobject representative of a second installed application corresponding toa second alert, wherein the first user interface object includes a firstaffordance that, when activated, launches the first installedapplication corresponding to the first alert, and wherein the seconduser interface object includes a second affordance that, when activated,launches the second installed application corresponding to the secondalert.
 33. The method of claim 32, wherein launching the first installedapplication or the second installed application comprises displaying thefirst installed application or the second installed application on thetouch-sensitive display.
 34. The method of claim 21, wherein thetouch-sensitive display comprises one or more sensors to detect anintensity of contacts with the touch-sensitive display, and wherein themethod further comprises: while displaying the notification interface,detecting a second contact on the display; determining whether acharacteristic intensity of the second contact is above a thresholdintensity; and in accordance with a determination that thecharacteristic intensity of the second contact is above the thresholdintensity, displaying an affordance for removing the plurality ofnotifications from the notification interface.
 35. The method of claim34, further comprising: in accordance with a determination that thecharacteristic intensity of the second contact is below the thresholdintensity and in accordance with a determination that the second contactis at a location on the display corresponding to a third notification ofthe plurality of notifications, wherein the third notificationrepresents a third alert of the plurality of alerts, and wherein thethird alert comprises third content: ceasing to display the notificationinterface; and displaying the third content.
 36. The method of claim 21,wherein the plurality of alerts comprises a location-based alert, andwherein displaying the notification interface comprises displaying anotification representing the location-based alert at a top of thenotification interface regardless of a value of any date-time associatedwith the location-based alert.
 37. The method of claim 21, whereindisplaying the notification interface includes replacing display of afirst set of user interface objects with display of the notificationinterface.
 38. The method of claim 21, wherein the indication, which isin the fixed location on a side of the display and adjacent to therotatable input mechanism, is offset from a center of the side of thetouch-sensitive display.
 39. The method of claim 21, wherein: theconcurrently displayed additional notifications comprise a firstnotification and a second notification, and a height of the stationaryuser interface object is not greater than a height of the firstnotification and is not greater than a height of the secondnotification.
 40. The method of claim 39, wherein the first notificationand the second notification collectively have a collective height thatis greater than half a height of the touch-sensitive display.
 41. Awearable electronic device, comprising: a touch-sensitive display; arotatable input mechanism that is physically rotatable relative to ahousing of the electronic device and adjacent to the display; one ormore processors; a memory; and one or more programs, wherein the one ormore programs are stored in the memory and configured to be executed bythe one or more processors, the one or more programs includinginstructions for: receiving a plurality of alerts, wherein the alertsinclude content, and wherein the alerts correspond to a plurality ofinstalled applications; detecting a user input; in response to detectingthe user input, displaying a notification interface on the display, thenotification interface comprising a plurality of notificationsrepresenting at least a subset of the plurality of alerts; whiledisplaying the notification interface, detecting a second user inputthat includes a first rotation of the rotatable input mechanism relativeto the housing of the electronic device; and in response to detectingthe second user input that includes the first rotation of the rotatableinput mechanism relative to the housing of the electronic device:scrolling the notification interface in a first direction in accordancewith the second user input, based on an amount of the first rotation ofthe rotatable input mechanism relative to the housing of the electronicdevice, to concurrently display additional notifications representingadditional alerts in the plurality of alerts; and displaying anindication determined in accordance with a plurality of currentlydisplayed notifications relative to an entire set of notificationsassociated with the plurality of received alerts, wherein the indicationcomprises a stationary user interface object representative of theentire set of notifications and a movable user interface objectrepresentative of the plurality of currently displayed notifications,wherein the stationary user interface object is displayed in a fixedlocation while scrolling the notification interface in the firstdirection in accordance with the second input, wherein the movable userinterface object moves relative to the stationary user interface objectwhile scrolling the notification interface in the first direction inaccordance with the second input, wherein a height of the stationaryuser interface object is not greater than a height of at least onenotification of the concurrently displayed additional notifications,wherein the stationary user interface object and the movable userinterface object were not displayed on the display prior to detectingthe second user input, and wherein the fixed location is adjacent to therotatable input mechanism that is physically rotatable relative to thehousing of the electronic device.
 42. The electronic device of claim 41,wherein the indication is representative of a position of the currentlydisplayed notifications relative to the entire set of notifications. 43.The electronic device of claim 41, wherein the indication isrepresentative of a proportion of the currently displayed notificationscompared to the entire set of notifications.
 44. The electronic deviceof claim 41, wherein the indication is displayed over at least a portionof one or more of the notifications.
 45. The electronic device of claim41, the one or more programs further including instructions for: inaccordance with a determination that rotational input is not detected,via the rotatable input mechanism, for a predetermined amount of time ofinactivity after detecting the second user input that includes the firstrotation of the rotatable input mechanism relative to the housing of theelectronic device, ceasing to display the indication.
 46. The electronicdevice of claim 45, wherein the indication is ceased to be displayed byfading out the indication over time.
 47. The electronic device of claim41, the one or more programs further including instructions for: whiledisplaying the notification interface, detecting a touch on thetouch-sensitive display and detecting a second rotation of the rotatableinput mechanism; and in response to detecting the touch and the secondrotation, zooming the notification interface.
 48. The electronic deviceof claim 47, wherein the touch and at least a portion of the secondrotation are detected simultaneously.
 49. The electronic device of claim41, wherein the plurality of notifications includes a first notificationcorresponding to a first alert, wherein the first alert comprises firstcontent, and wherein the one or more programs further includeinstructions for: detecting a first contact on the first notification;and in response to detecting the first contact on the firstnotification: ceasing to display the notification interface; anddisplaying the first content.
 50. The electronic device of claim 49,wherein the first contact on the first notification is detected on auser interface object representative of a corresponding installedapplication of the first alert.
 51. The electronic device of claim 49,the one or more programs further including instructions for: afterdisplaying the first content, detect a third user input; and in responseto detecting the third user input: re-displaying the notificationinterface, wherein the notification interface excludes the firstnotification.
 52. The electronic device of claim 41, wherein theplurality of notifications includes a first notification and a secondnotification, wherein the first notification includes a first userinterface object representative of a first installed applicationcorresponding to a first alert and the second notification includes asecond user interface object representative of a second installedapplication corresponding to a second alert, wherein the first userinterface object includes a first affordance that, when activated,launches the first installed application corresponding to the firstalert, and wherein the second user interface object includes a secondaffordance that, when activated, launches the second installedapplication corresponding to the second alert.
 53. The electronic deviceof claim 52, wherein launching the first installed application or thesecond installed application comprises displaying the first installedapplication or the second installed application on the touch-sensitivedisplay.
 54. The electronic device of claim 41, wherein thetouch-sensitive display comprises one or more sensors to detect anintensity of contacts with the touch-sensitive display, and wherein theone or more programs further include instructions for: while displayingthe notification interface, detecting a second contact on the display;determining whether a characteristic intensity of the second contact isabove a threshold intensity; and in accordance with a determination thatthe characteristic intensity of the second contact is above thethreshold intensity, displaying an affordance for removing the pluralityof notifications from the notification interface.
 55. The electronicdevice of claim 54, the one or more programs further includinginstructions for: in accordance with a determination that thecharacteristic intensity of the second contact is below the thresholdintensity and in accordance with a determination that the second contactis at a location on the display corresponding to a third notification ofthe plurality of notifications, wherein the third notificationrepresents a third alert of the plurality of alerts, and wherein thethird alert comprises third content: ceasing to display the notificationinterface; and displaying the third content.
 56. The electronic deviceof claim 41, wherein the plurality of alerts comprises a location-basedalert, and wherein displaying the notification interface comprisesdisplaying a notification representing the location-based alert at a topof the notification interface regardless of a value of any date-timeassociated with the location-based alert.
 57. The electronic device ofclaim 41, wherein displaying the notification interface includesreplacing display of a first set of user interface objects with displayof the notification interface.
 58. The electronic device of claim 41,wherein the indication, which is in the fixed location on a side of thedisplay and adjacent to the rotatable input mechanism, is offset from acenter of the side of the touch-sensitive display.
 59. The electronicdevice of claim 41, wherein: the concurrently displayed additionalnotifications comprise a first notification and a second notification,and a height of the stationary user interface object is not greater thana height of the first notification and is not greater than a height ofthe second notification.
 60. The electronic device of claim 59, whereinthe first notification and the second notification collectively have acollective height that is greater than half a height of thetouch-sensitive display.